Re: [PATCH 6/6] Teach core object handling functions about gitlinks

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

 



hoi :)

On Thu, Apr 12, 2007 at 12:12:59PM +1200, Sam Vilain wrote:
> Linus Torvalds wrote:
> > So there's a very real issue where a repository with submodules still 
> > "works", even with a .gitmodules file that is totally scrogged and doesn't 
> > have the right information (yet), it's just that it may simply not be able 
> > to do all the operations because it cannot figure out where to pull 
> > missing subproject data from etc..
> >   
> 
> Whoa... "missing" subproject data?
> 
> Surely, unless you're doing lightweight/shallow clones, if you have a
> gitlink you've also got the dependent repository? Otherwise the
> reachability rule will be broken.

With submodules you actually have a natural cutting point where
you can say: no, I don't want to get that.
So for submodules the reachability rule is a little bit more relaxed.

And when you fetch the superproject you now need some way to fetch
the new submodule objects.  They may be in the same upstream repository
but it may make sense to have this configurable.

-- 
Martin Waitz

Attachment: signature.asc
Description: Digital signature


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