Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: infrastructure-dev@apache.org
Received-SPF: neutral (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=jH3sM2yWzKbqrDataVUN9C4bvj+E96m/B+PlKZMwpErB/HvBSY3vmkmzT0OTp3i5Hoff/YTLg1WN/eW5LvQX4INKdeN5qZUXe8KZ5Z+ldgiX2XJF9PuIluMGPflE3Kh/qPX9ZyP8UVS0965QB8IO+YsopEayzgUTB8+hu2SANAk=;
Message-ID: <291389.15192.qm@web27807.mail.ukl.yahoo.com>
Date: Wed, 10 Jun 2009 09:57:06 +0000 (GMT)
From: Mark Struberg <struberg@yahoo.de>
Subject: Re: Servicemix git repository
To: infrastructure-dev@apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


you may take a look at git-submodules [1] for bundling multiple git-repos t=
ogether into one 'package'

But unfortunately I doubt this will work with git-svn and dcommit over the =
whole repo. Doing a dcommit in a single submodule should work just fine!

LieGrue,
strub

[1] http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html


--- Santiago Gala <santiago.gala@gmail.com> schrieb am Mi, 10.6.2009:

> Von: Santiago Gala <santiago.gala@gmail.com>
> Betreff: Re: Servicemix git repository
> An: infrastructure-dev@apache.org
> Datum: Mittwoch, 10. Juni 2009, 11:35
> El mar, 09-06-2009 a las 22:43 +0200,
> Jukka Zitting escribi=F3:
> > Hi,
> >=20
> > On Tue, Jun 9, 2009 at 8:04 PM, Santiago Gala<santiago.gala@gmail.com>
> wrote:
> > > If there is a semi-automated way to get the bunch
> of repos I might try
> > > to merge them into one big "all-in-one" repo, for
> people to experiment.
> > > Depending on results, either approach is valid
> >=20
> > It might be an interesting exercise, but I'd rather
> keep the mapping
> > between svn and git as simple and straightforward as
> possible.
> >=20
>=20
> No problem
>=20
> > If the ServiceMix people think it's a good idea to
> have just a single
> > repository, they could move all their code into a
> single svn trunk.
> > But I'm sure there's a good reason to keep all those
> codebases
> > separate.
> >=20
>=20
> Well, even with a single git repository, only *one* tree
> can be checked
> out at a time. In such a set up, to get several checkouts
> from the same
> repository would require using environment variable
> (GIT_DIR), etc.
>=20
> In a sense, such a git set up would keep all those
> codebases separate
> *in the same repository*.
>=20
> But my proposal was highly speculative, no need to go
> there
>=20
> Regards
> Santiago
>=20
>=20
> > BR,
> >=20
> > Jukka Zitting
>=20
> =0A=0A=0A