git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kyle J. McKay" <mackyle@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git mailing list <git@vger.kernel.org>,
	Scott Chacon <schacon@gmail.com>,
	Johan Herland <johan@herland.net>, Jeff King <peff@peff.net>
Subject: Re: [PATCH v2 2/2] t/t3308-notes-merge.sh: succeed with relaxed notes refs
Date: Tue, 6 Jan 2015 17:27:03 -0800	[thread overview]
Message-ID: <27162E6E-742C-455D-A005-220B7A8B38CF@gmail.com> (raw)
In-Reply-To: <xmqqoaqbmpmj.fsf@gitster.dls.corp.google.com>

On Jan 6, 2015, at 15:54, Junio C Hamano wrote:

> "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?

  reply	other threads:[~2015-01-07  1:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06  8:03 [PATCH v2 0/2] Accept any notes ref Kyle J. McKay
2015-01-06  8:03 ` [PATCH v2 1/2] notes: accept any ref Kyle J. McKay
2015-01-06  8:03 ` [PATCH v2 2/2] t/t3308-notes-merge.sh: succeed with relaxed notes refs Kyle J. McKay
2015-01-06 10:20   ` Junio C Hamano
2015-01-06 12:27     ` Kyle J. McKay
2015-01-06 18:25       ` Junio C Hamano
2015-01-06 23:29         ` Kyle J. McKay
2015-01-06 23:54           ` Junio C Hamano
2015-01-07  1:27             ` Kyle J. McKay [this message]
2015-01-07  0:28           ` Johan Herland
2015-01-07  1:51             ` Kyle J. McKay
2015-01-07 16:14             ` Junio C Hamano
2015-01-07  1:19       ` Johan Herland
2015-01-07  1:19     ` Jeff King
2015-01-07 16:03       ` Junio C Hamano
2015-01-08 10:31         ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=27162E6E-742C-455D-A005-220B7A8B38CF@gmail.com \
    --to=mackyle@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johan@herland.net \
    --cc=peff@peff.net \
    --cc=schacon@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).