Location-agnostic submodules

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

I just discovered the workings of the submodule command, and as I have
grown to like the fact that a repository is not unique with Git, and
specifically that it has no unique or central location, I'm bothered
by how submodule works.

Would there be any major issue in having (1) submodule to be able to
clone the submodules from the super repository when they are available
there and (2) having zero, one or many addresses for each submodule,
used as hints (obviously not used when (1) is satisfied)?

When the repository is not bare, the submodules would be found at
their place in the tree, nothing difficult here. When the repository
is bare, there could be a tree with the bare repositories of the

This could be done by a new subcommand, that would take a remote as an
optional argument, its default being origin, as usual:

$ git submodule clone origin

As I see it, adding this 'clone' subcommand for the case where the
repository is not bare couldn't add any compatibility issue, so if I'm
right on this point, I'd like to try and implement this soon.

OpenPGP 0xD9D50D8A

Attachment: signature.asc
Description: Digital signature

[Newbies FAQ]     [Linux Kernel Development]     [Free Online Dating]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Free Online Dating]     [Photo]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]     [Linux Resources]

Add to Google