> On 2018-03-15, at 11:37, Marko Mäkelä <msmakela@gmail.com> wrote: > > 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. That reminds me of my original concerns, some years ago when I started to work with git. They were almost exactly the same. But - frankly - I have already long forgotten why I felt so bad about letting some of the old habits go :-) The major (and unsolvable properly) problem with git is moving files around (includes renaming) and keeping their full history while doing so. See the rant I mentioned: https://tinyurl.com/yapz4xuw There is no "proper" solution to that, unless you use your repository as private one and you can notify all collaborators / tools maintainers about the change. Then the approach listed there works. But if you post your repository as public, there is no good solution. But you know what? I learned to live with that somehow. I guess I just became less attached to the full history of all, each and every file, which - to be totally honest - has yet to prove being useful after some decades of working with VCSs. -- SD!Received on 2018-03-15 13:03:15
Archive generated by hypermail 2.2.0.