commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <>
Subject Re: [cli] Moving to Git?
Date Tue, 26 Nov 2013 14:23:35 GMT
On Tue, Nov 26, 2013 at 8:56 AM, Gilles <>wrote:

> On Tue, 26 Nov 2013 14:47:09 +0100, Emmanuel Bourg wrote:
>> Le 26/11/2013 14:42, Benedikt Ritter a écrit :
>>  What's the point of using git then?
>> To provide a better collaboration tool for the external contributors,
>> and thus increasing the external contributions?
> Unless I missed some of the recent discussions, this point has been
> argued against and no counter-argument was presented.
> For reminder, the argument was that it is quite easy to provide a
> contribution with Subversion:
> $ svn co "<URL>"
> $ cd  trunk
> $ mvn test
> $ svn diff > "issue<xxxx>.patch"
> Using a different source management system must bring added value to
> the project (IOW: the regular developers).

For me, this is not about one VCS vs. another, it's about having more than
one, which we currently support.

>From a process standpoint, today I see a lot (1/2?) of patches come in
through Git (either as a pull request or a patch).

When it's a Git patch file, I have to manually fiddle with the patch file
to make it an SVN patch file, which is a pain. If it's a pull request, it's
more fiddling.

Personally, I do not see the point of mirroring our SVN stuff to Git, it
makes the process more complicated for me. But, Git is popular and the way
of the future, there is no unringing that bell. Fine, let's move forward.
Git seems more like another way to make our code more public. To that end,
it would seem simpler to switch to Git (hosted at Apache) so that the
process of sharing code and patches is less painful. This means getting rid
of SVN.

So my point is not that have we need to show that using Git is better, it's
that now, having BOTH SVN and Git is a pain.


> Best regards,
> Gilles
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

E-Mail: |
Java Persistence with Hibernate, Second Edition<>
JUnit in Action, Second Edition <>
Spring Batch in Action <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message