Re: [PATCHv5 2/4] Add infrastructure for ref namespaces

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

 



Jamey Sharp <jamey@xxxxxxxxxxx> writes:

> Note that namespaces which include a / will expand to a hierarchy of
> namespaces; for example, GIT_NAMESPACE=foo/bar will store refs under
> refs/namespaces/foo/refs/namespaces/bar/.  This makes GIT_NAMESPACE
> behave hierarchically, and avoids ambiguity with namespaces such as
> foo/refs/heads.

I would have expected that this explanation would be improved after you
having to answer my question on the list.  Otherwise it was a wasted
effort, for both me (asking) and you (answering).

>
> This adds the infrastructure for ref namespaces: handling the
> GIT_NAMESPACE environment variable and --namespace option, and iterating
> over refs in a namespace.  Subsequent commits use this infrastructure to
> implement the user-visible support for ref namespaces.
>
> Commit by Josh Triplett and Jamey Sharp.

Also please drop that "Commit by ...".  We can read Sign-off.
--
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]