Re: Notes on Using Git with Subprojects

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

 



Hi,

On Wed, 27 Sep 2006, Shawn Pearce wrote:

> A Large Angry SCM <gitzilla@xxxxxxxxx> wrote:
> > Jeff King wrote:
> > [...]
> > >One thing that I believe some people have requested for subprojects is
> > >to avoid downloading files/history for subprojects you're not interested
> > >in.  I think this could be faciliated in this scheme by only cloning the
> > >heads of the subprojects you're interested in (there would need to be
> > >special machinery to handle this at the root level if we want to allow
> > >making root commits without necessarily having all of the subprojects).
> > 
> > In what I'm suggesting, commits are local to a project's working 
> > directory repository and are pushed somewhere else to be recorded long 
> > term. Since projects are stand alone, possibly with dependencies, 
> > working on a (sub)project without having other associated (sub)projects 
> > is accomplished by checking it out.
> > 
> > >A first step to this would be an argument to git-clone to allow cloning
> > >only a subset of refs.
> > 
> > Something like this?
> > 
> > 	git-init-db
> > 	git-fetch <repository> <refspecs>
> 
> More like:
> 
>  	git-init-db
>  	git-fetch --keep <repository> <refspecs>
> 
> but yes.  :-)

You are missing the remotes/ information:

git-repo-config remote.origin.url <repository>
for spec in <refspecs>; do
	git-repo-config remote.origin.fetch $spec ^$
done

Ciao,
Dscho

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