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

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

 




On Apr 11, 2007, at 7:54 PM, Martin Waitz wrote:

Before submodules:
tree <-> index <-> working file

submodules always using HEAD:
tree <-> index <-> submodule HEAD <-> submodule working dir

submodules using some dedicated branch:
tree <-> index <-> subm. "from-supermodule" <-> subm. HEAD <-> subm. wd

Why can't can't we extend checkout with an option to look for an enclosing git project, find the gitlink in the index, and check out that commit? That allows you to return to the original state without needing to bother with new special branches.

And instead of recording the path in a .gitmodules file, why not a list of git directories we search for the commit? Allows moving of subprojects without suddenly breaking configuration files. When we find the appropriate git dir, we can use a .gitlink file or symlinks to attach the directory to it's repository.

I dislike moving git in the direction of enforcing more policy instead of less, and of making it less capable of handling content movement instead of more.

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