Mailing-List: contact couchdb-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates
 64.233.184.226 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=raAfotWtH9yaM2mi3WfwUb5pZhHFoHMzseBO1ttquP5QjvNhFTjenp+pDCWxdU8r+/
         H2PHdbYeFHP9wVvEvWuIrE5T1yMlyNNf5V9U5Wkq6Di7VdlNqadQ0VSrfVRWcHMzPIw1
         Ww2/yNn9V1IxEOk6VVjwCLfZktYOsX4eWFSOU=
Message-ID: <e282921e0810020035q3152af2ag48aa17320e94a1e6@mail.gmail.com>
Date: Thu, 2 Oct 2008 00:35:23 -0700
From: "Chris Anderson" <jchris@apache.org>
Sender: jchris@gmail.com
To: couchdb-dev@incubator.apache.org
Subject: Re: git vs. svn (Was: command line test runner)
In-Reply-To: <510143ac0810020007t4fa6b9e7q6d939b1273284323@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <510143ac0810020007t4fa6b9e7q6d939b1273284323@mail.gmail.com>

On Thu, Oct 2, 2008 at 12:07 AM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> Hi,
>
> Background: I'm gathering data on cases where people prefer to use git
> over svn for Apache development.
>
> On Thu, Oct 2, 2008 at 8:59 AM, Chris Anderson <jchris@apache.org> wrote:
>> Here is the git-branch I'm developing in for now:
>
> You're an Apache committer, so you could also have used an svn branch
> for this. Are there particular reasons why you prefer to use git?
>

Thanks for the question! I like to use git for more experimental work,
especially where I'll be doing a lot of small commits. Committing to
svn spews into the bug tracker and mailing list. Also, when I'm
experimenting, its easier not to worry about the Apache formalities
like license in every file (especially when those files may never end
up in the project).

A new reason is that I've found that git (and github) make it much
more likely that I'll receive patches from interested users, rather
than just feature requests.

So generally I like to work in git where I have fine-grained control,
and then compose a patch to apply to the svn repository once I know it
is work I'll stand behind.

That said, I'm a new committer, so this is the workflow I developed
before I received my pre-commit-bit. However, I'm happy with this
workflow, and I think it's certainly better than the alternative,
which would likely be just keeping the work on my local machine until
I think it's ready for prime time.

Chris

-- 
Chris Anderson
http://jchris.mfdz.com