Hi Steve,
> Ales, I understand your planning to cut over to git. How are your
> experiences with the server side? I've played some with git-cvsimport
Given that I'm using debian on the server side, I had very little
problems getting git-daemon and gitweb up and running.
> (it does indeed preserve the CVS history) and I'm satisfied and
> I've put together sample git-daemon access to a repository made up
> from current anoncvs. Have you concluded it makes sense to run a
> repository to track CVS for a while, or are you just cutting over?
I'm going to run a git-cvsserver for a little bit (or longer depending
on the feedback) just to give some time for adjustment. If people
stop using it, I'll do git exclusively. If git annoys too many people,
I'll try something else. Basically, git is on probation, until it
proves itself. However, I'm quite optimistic that the branching
capabilities will make up for a lot.
>
> Has the movement to git generated any hate mail?
Not really.
>
> How are you planning to offer write ("push") access to the repository?
Yes. As far as I can tell, I will need to setup restricted ssh access to
the git machine. Any gEDA developer who currently has write access to
the gEDA/gaf CVS repository will continue to have write access to the git
repository.
I haven't actually tried setting this up (push access or git-cvsserver),
but that will be my first task on Saturday's code sprint.
I'll have a better feel for this git transition after Saturday. Btw,
I won't be doing anything with the existing CVS repository until after
the sprint, so, developers, please feel free to commit away. I will
be doing some testing with the Peters to make sure the transition will
be smooth.
-Ales
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
