[logback-dev] Git as a version control system?
ceki at qos.ch
Fri Aug 7 09:59:45 CEST 2009
While I agree that tool support around git is still lacking, given its
rising popularity, tool support will eventually follow. From what I
know, it is possible to keep an SVN repository synchronized with a git
repository. Thus, during a transitional period (which may last several
years), we could publicize both an SVN and a git repository.
My question is then whether moving to git is worth the trouble and
whether it will encourage contributions by making it easier for
developers to contribute. From a strictly personal point of view, the
fact that git works in disconnected mode is a killer feature.
Robert Elliot wrote:
> I really value tool support; the Maven & Subversion combination has
> really only just reached maturity on Eclipse with Subversive and
> M2Eclipse integrating properly and allowing you to check a Maven project
> out from Subversion and have M2Eclipse sort out your classpath and
> project structure for you with no further input. This (for me at least)
> dramatically reduces the barrier to entry and makes me vastly more
> inclined to pull down a project and have a look under the hood, and
> maybe get involved. An admittedly cursory check of the net suggests
> that git does not integrate so well with M2Eclipse (there's no mention
> of it on the M2Eclipse site or wiki).
> On 6 Aug 2009, at 20:04, Ceki Gulcu wrote:
>> Hi all,
>> I was wondering if we should be moving to git as our version control
>> I really like the fact that git's repository is stored on the local
>> disk. It also appears that git makes it easier for developers to
>> contribute patches. Could anybody confirm or care to share their
>> experiences with git? Is there anyone against using git?
Logback: The reliable, generic, fast and flexible logging framework for Java.
More information about the logback-dev