RE: Git-new-workdir
- From
- Craig L. Ching <cching@mqsoftware.com>
- Date
- May 21, 2008, 18:57 UTC
- Message-ID
- <63BEA5E623E09F4D92233FB12A9F794301FC8B24@emailmn.mqsoftware.com>
- In-Reply-To
- <20080521184446.GA23924@bit.office.eurotux.com>
> From: Luciano Rocha [mailto:luciano@eurotux.com] > On Wed, May 21, 2008 at 01:21:22PM -0500, Craig L. Ching wrote: > > Hi all, > >
[stuff about why we want to use git-new-workdir]
Show 13 quoted lines
> > Personally, I'd clone a local rep for each build, with the -s > option to clone. > > Something like: > > git clone server:/rep ~/master > git clone -s ~/master build/abc > git clone -s ~/master build/foo > ... > > The -s option should reduce disk-usage considerably. >
Yeah, I neglected to mention that the other good thing about git-new-workdir is that the origin is set to the origin of the remote repository so to push changes to our central repository, you only need one push. Otherwise you have to push twice, right? Well now (thinking out loud here), maybe you don't. That was the impression I got from the IRC conversation, but maybe you could just push from the original clone? Still, seems easier if all the shared repositories and the original clone pushed to the same place, at least for us.
Show 5 quoted lines
> -- > Luciano Rocha <luciano@eurotux.com> > Eurotux Informática, S.A. <http://www.eurotux.com/> > >
Thanks for the feedback, it's making me think about the problem ;-)
Cheers, Craig