I have never used Git.
If SVN is changed to Git, I will be totally lost and it means I would be
completely out of the project, while I am not sure you will be maintained it
in one month. For the moment I would prefer we keep SVN.
In the sametime, you are the most implied developpers so it is quite unfair
for you.
Is Git a priority for you or could you still stay with SVN? (Many commits is
not a real problem I think, compared to my lost from the project I mean :o))
Benjamin HUYNH KIM BANG
http://benjamin.hkb.fr/contact.htm
On Sun, Jan 10, 2010 at 7:00 PM, Christian Weiske <cw...@cw...>wrote:
> Hi all,
>
>
> I'd like to switch the versioning control system from currently SVN to
> git. At home or when travelling to/from work, I am mostly offline and
> need to do local commits, which is why I am using git locally and the
> git-svn gateway to commit to the official repository.
> This has some downsides, i.e. I completely loose the commit history
> timestamps and it always appears that I do 20 commits in two minutes.
> When working with patches from other people, we lose their contribution
> information since the commits seem to come from us. Also, branching is
> hard when using the git-svn gateway.
>
> Benjamin, what do you think? Could we switch?
>
> --
> Regards/Mit freundlichen Grüßen
> Christian Weiske
>
> -= Geeking around in the name of science since 1982 =-
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Semanticscuttle-devel mailing list
> Sem...@li...
> https://lists.sourceforge.net/lists/listinfo/semanticscuttle-devel
>
>
|
