On Jan 6, 2015, at 15:54, Junio C Hamano wrote:
"Kyle J. McKay" <mackyle@xxxxxxxxx> writes:
A whitelist solves issue (1) but is no help for issue (2) unless some
additional additional part of the refs namespace were to be also
whitelisted. Perhaps something like refs/x-<anything>/... in the
same
vein as the various IETF standards for experimental names.
Your (2) is about people who are _experimenting_, no?
Why can't they use refs/notes/x-<anything>/* while doing so, and
when that matures and proves useful to wider public we can make it
more official by whitelisting refs/<that-thing> in addition to
refs/notes/, and the problem is solved, no?
I supposed if that's the best that can be done. The problem is then
that if you set notes.displayRef to refs/notes/* to see all relevant
notes, don't you end up seeing these experimental, not-meant-for-end-
user-consumption notes if they are somewhere under refs/notes/ ? My
glob specs are a little fuzzy, maybe it's refs/notes/** that gets
everything under it?
--
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