Re: [PATCH v2 2/2] t/t3308-notes-merge.sh: succeed with relaxed notes refs
- From
Kyle J. McKay <mackyle@gmail.com>
- Date
- Jan 7, 2015, 01:27 UTC
- Message-ID
- <27162E6E-742C-455D-A005-220B7A8B38CF@gmail.com>
- In-Reply-To
- <xmqqoaqbmpmj.fsf@gitster.dls.corp.google.com>
On Jan 6, 2015, at 15:54, Junio C Hamano wrote:
Show 14 quoted lines
> "Kyle J. McKay" <mackyle@gmail.com> 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?