Hello, * On Thu, Mar 15, 2018 at 11:44:07AM +0100 silverdr@wfmh.org.pl wrote: > > > 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. git is also rsync-friendly, because normally, it does not change files that are already present. But, OTOH, why use rsync in the first place? git can be operated to create full clones. > It is definitely possible. For example Spiro here is also involved > with cc65, where a big transition from SVN to git has taken place some > time ago. To my understanding he participated in the process. Yep. It is very easy. There is a git-svn module. You can use it to create a git repository that tracks an SVN repository. You can even use it to handle your work in git, but commit it back to SVN. I have done this at work some years ago. It's very handy, especially as you have all the history on your machine while you are offline. I had used git-svn to track the SVN of the cc65 SVN of Uz. Then, I pushed it to github. That's why with cc65 on github, you have that "git-svn-id:" line in the old commits. The last commit before the full transition to git is the following: commit e6aa00b339e1f36ef6e05aa2238096c81307e779 Author: uz <uz@b7a2c559-68d2-44c3-8de9-860c34a00d81> Date: Wed Mar 6 12:53:07 2013 +0000 Reorder CF_xxx flags so that they can be used as table index. git-svn-id: svn://svn.cc65.org/cc65/trunk@5990 b7a2c559-68d2-44c3-8de9-860c34a00d81 There might be other ways, but it was the simplest one for me. Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/Received on 2018-03-15 23:00:24
Archive generated by hypermail 2.2.0.