[1068] in BarnOwl Developers
Re: [Poll] Moving to git
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Thu Oct 29 18:12:41 2009
Resent-From: nelhage@mit.edu
Resent-To: barnowl-dev-mtg@charon.mit.edu
X-Original-To: nelhage@nelhage.com
Date: Fri, 30 May 2008 16:20:40 -0400 (EDT)
From: Geoffrey Thomas <geofft@MIT.EDU>
To: Nelson Elhage <nelhage@mit.edu>
cc: dirty-owl-hackers@mit.edu
In-Reply-To: <20080527231200.GA11844@mit.edu>
I don't know if it's a big enough project to warrant switching, although
I'd be fine either way. Would using git make it easier for people to
maintain their own modules in a way that integrates well with the main
repository?
--
Geoffrey Thomas
geofft@mit.edu
On Tue, 27 May 2008, Nelson Elhage wrote:
> I haven't seen any responses to this. Does anyone have opinions about
> whether or not they would want to see barnowl move to git, or is
> everyone completely indifferent?
>
> - Nelson
>
> On Thu, May 15, 2008 at 05:07:36PM -0400, Nelson Elhage wrote:
>> There's been some suggestion of moving the barnowl source repository
>> to git, instead of svn. I'm personally already using git to develop
>> barnowl, using git-svn to move changes back and forth.
>>
>> I'm mostly happy with svn, but branching and merging is a bit of a
>> pain, even with svnmerge; I think the ability to branch and merge much
>> more easily would be the main advantage to git.
>>
>> The main disadvantage is that git is still relatively young and more
>> annoying to work with in some ways; For instance, it can create really
>> convoluted merge histories unless everyone is always careful to
>> git-rebase rather than merging where appropriate, which also has some
>> potential negative consequences.
>>
>> Does anyone here have a strong opinion either way?
>>
>> - Nelson
>>
>
