On Wed, Sep 16, 2015 at 3:34 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Jacob Keller <jacob.e.keller@xxxxxxxxx> writes: > >> From: Jacob Keller <jacob.keller@xxxxxxxxx> >> >> The documentation for --refs says that it will treat unqualified refs as >> under refs/notes. Current behavior is to prefix refs/notes to all >> strings that do not start with refs/notes or notes/, resulting in >> performing actions on refs such as "refs/notes/refs/foo/bar" instead of >> attempting to perform actions on "refs/foo/bar". > > That actually sounds like a sensible thing to do, if you replace > 'foo' with 'heads', for example, i.e. refs/notes/refs/heads/bar is a > notes about commits reachable from the branch whose name is 'bar'. > > So given "refs/heads/bar", which is unqualified in the context of > talking about references that hold notes trees, the current > behaviour to turn it into "refs/notes/refs/heads/bar" is very > sensible, I would think. > I never got any better suggestion on how to allow the behavior desired, which is to enable merging from a non-notes location, in order to provide a standard location for remote notes, ie: refs/remote-notes/<remote>/<ref> Any suggestions, if you're against this particular change? Regards, Jake -- 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