2013/6/14 Christian Grobmeier :
> Hello,
>
> I would like to collect some feelings on GIT here. We have discussed a
> bit to move on to Git for S3. If we would vote on it today, what would
> you vote?
>
> Personally I would vote +1.
>
> There is of course a risk that things become complicated first
Hi all,
my team has moved from CVS to GIT few months ago
and besides the obvious benefits
there are two things that surprised us.
One is the speed of working with GIT,
we were hoping to get more speedup
and after the transition only branching is faster.
Second thing is complication of versioning
+1 all 'round; the ability to work off-line on multiple branches, the
ability to cherry-pick merges, etc. is so helpful.
I haven't done anything with versioned releases, not am I sure what the
best practice is.
I have started using gitflow too, which seems nice, and a decent way to
normalize proc
bilité
pour le contenu fourni.
> From: grobme...@gmail.com
> Date: Fri, 14 Jun 2013 10:13:11 +0200
> Subject: Emotions on GIT @ Struts
> To: dev@struts.apache.org
>
> Hello,
>
> I would like to collect some feelings on GIT here. We have discussed a
> bit to move on to G
Hello,
I would like to collect some feelings on GIT here. We have discussed a
bit to move on to Git for S3. If we would vote on it today, what would
you vote?
Personally I would vote +1.
There is of course a risk that things become complicated first. But
there is a lot of experience with in ASF