On Thu, Mar 15, 2018 at 09:52:42AM +0000, smf wrote: >The last time I looked github doesn't allow you to follow renames when >looking at history on their web interface, it's also limited in terms >of number of files it will show you in a directory. We've just sucked >it up for the moment and haven't looked at switching, the others might >suffer the same problem. I believe that this is an inherent limitation of the git repository format. My understanding is that unlike bzr and svn, git does not really track renames. There is no concept like the bzr file-id. Also there is nothing that directly corresponds to the "svn copy" operation. If you copy and modify a file, "git blame" would not show the original history of the file, while "svn blame" would. Also bzr never implemented "bzr copy". By having a simpler repository format, git is making it a little easier for the writers, and harder for readers who are interested in tracking changes. Also, thanks to the simpler format, switching between arbitrary revisions as well as operations like "git grep" or "git log -G" are very fast. I am not aware of these operations existing in svn or bzr, or maybe they would be so slow that they would be useless. >The horrible git clients are IMO more of an issue. TortoiseGit on >windows sucks pretty bad, but it's still the best graphical ui client I >tried. Using a command line tool would take too much time out of my >day. I am pretty happy with the git command-line tools as well as the integration with GNU Emacs. >I'd still use git though, because having to remember how to use two >horrible source control systems is too much hassle. I guess I should convert my svn repositories to git and upload to GitHub. I already have a work-related account there. The point that each checked out copy of the repository is a full backup of the history is very valid, and works like an insurance if the free-as-in-beer service of the closed-source GitHub goes away. I should also find out if there are any usable svn-to-git gateways. I would prefer to keep my own repositories in svn fsfs format, because it is very rsync-friendly for making backups: each commit is 2 new files with understandable names (svn revision is the number of commits since the start). The git repository format with lots of files named by some hash values is totally opaque to me. MarkoReceived on 2018-03-15 12:03:52
Archive generated by hypermail 2.2.0.