Re: .gitlink for Summer of Code

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

 



On Monday 26 March 2007, Matthieu Moy wrote:
> Josef Weidendorfer <Josef.Weidendorfer@xxxxxx> writes:
> > The original proposal was to have a standard .git directory for every
> > light-weight checkout inside of the base .git directory, e.g.
> > in <base>/.git/ext/<name>.git where <name> is some identifier for the
> > lightweight checkout, either provided in the .gitlink file or
> > automatically determined.
> 
> That seems really weird. That implies for example:
> [... some good reasons to not do it this way ...]

Ok, you are right.
It is better to not touch the original repository
for lightweight checkouts.

> * You have to manage a name for each lightweight checkout. What would
>   be such name? User-provided? uuidgen-like?

Such a name is interesting as identifier for submodules.
It would be the relative path of the submodule from the supermodule base;
or user supplied.

Lightweight checkouts and submodules have different requirements;
yet, the lightweight checkouts should be so flexible to be
able to be used for submodules checkouts.

Josef

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