Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
From: Knut Anders Hatlen <knut.hatlen@oracle.com>
To: derby-dev@db.apache.org
Subject: Re: Git mirror for Derby
References: <x6hb7n6zm8.fsf@oracle.com>
Mail-Followup-To: derby-dev@db.apache.org
Date: Sat, 18 Jun 2011 19:10:52 +0200
In-Reply-To: <x6hb7n6zm8.fsf@oracle.com> (Knut Anders Hatlen's message of
	"Sat, 18 Jun 2011 15:25:03 +0200")
Message-ID: <x662o36p5v.fsf@oracle.com>
User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (usg-unix-v)
MIME-Version: 1.0
Content-Type: text/plain

Knut Anders Hatlen <knut.hatlen@oracle.com> writes:

> Hi all,
>
> The infrastructure team has set up a read-only Git mirror of the Derby
> code repository at http://git.apache.org. The Git repository will be
> useful when doing code archaeology, since you'll have the entire history
> stored locally so log, blame/annotate, diffing old revisions and binary
> search should be a lot faster than doing the same operations against the
> Subversion repository. It may also be a useful tool for managing patches
> when working on multiple issues.
>
> Some links to get started:
>
> http://www.apache.org/dev/git.html
> http://wiki.apache.org/general/GitAtApache

A quick update: I cloned the Git mirror and followed the instructions in
the above links on how to commit changes from Git to the Subversion
repository. I tested it out with the patch for DERBY-5217, and the
changes appear to have been successfully propagated to the Subversion
repository after running "git svn dcommit":
http://svn.apache.org/viewvc?view=revision&revision=1137213

-- 
Knut Anders