Re: [RFC] Fourth round of support for cloning submodules

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

 



On Thu, May 24, 2007 at 12:31:33PM +0100, Johannes Schindelin wrote:
> On Thu, 24 May 2007, Sven Verdoolaege wrote:
> > OK... so what should git-update-server-info put in this file for submodules?
> > Or, equivalently, what should be the output of ls-remote?
> > 
> > Right now its a list of pairs of revs(sha1) and refs.
> > For submodules we want a connection between a submodule name
> > and one or more URLs where the submodule can be found.
> > How are you going to squeeze that into info/refs without confusing
> > older versions of git?
> 
> I wonder if the "ref^{blub}" syntax could be used for that: change "blub" 
> to the URL, or "sub:URL" or something.

Just to be clear, would it look like the following?

e8a6e39ecfbd391a54b9c3329fd3c6e33d745abd	refs/heads/bernstein
c5c64e3fe48302f0c4581985f9c68d615f7bcb4e	refs/heads/master
3fa7ded19a8da868d3af7c942f86358e6720f0c7	refs/heads/submodule
/home/sverdool/public_html/cloog.git	cloog^{URL}
http://www.liacs.nl/~sverdool/cloog.git	cloog^{URL}

Is there no code out there that expects the "rev" part to be
exactly 40 characters?
Or do you propose we put the URL in a blob and put the object sha1
in there.  If so, who's going to create these blobs for the git://
and ssh:// protocols?  upload-pack?

Thanks for the discussion, btw.
I hope we can come up with something that's acceptable to everyone.

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