RE: Git-new-workdir

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 

> From: Luciano Rocha [mailto:luciano@xxxxxxxxxxx] 
> 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]

> 
> 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.

> --
> Luciano Rocha <luciano@xxxxxxxxxxx>
> Eurotux Informática, S.A. <http://www.eurotux.com/>
> 
> 

Thanks for the feedback, it's making me think about the problem ;-)

Cheers,
Craig
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux