Re: [PATCH] notes: document behavior of --ref and --notes DWIMery

2015-09-22 Thread Junio C Hamano
"Keller, Jacob E" writes: > On Tue, 2015-09-22 at 13:40 -0700, Junio C Hamano wrote: >> How about phrasing it totally differently? >> >> The ref specifies the full refname when it begins with >> `refs/notes/`; otherwise `ref/notes/` is prefixed to form a >> full name of the ref. >

Re: [PATCH] notes: document behavior of --ref and --notes DWIMery

2015-09-22 Thread Keller, Jacob E
On Tue, 2015-09-22 at 13:40 -0700, Junio C Hamano wrote: > How about phrasing it totally differently? > > The ref specifies the full refname when it begins with > `refs/notes/`; otherwise `ref/notes/` is prefixed to form a > full name of the ref. > > I think that would remove th

Re: [PATCH] notes: document behavior of --ref and --notes DWIMery

2015-09-22 Thread Keller, Jacob E
On Tue, 2015-09-22 at 13:40 -0700, Junio C Hamano wrote: > Jacob Keller writes: > > > From: Jacob Keller > > > > The --notes and --ref parameter for selecting which notes ref to > > operate > > on are based off of expand_notes_ref functionality. The > > documentation > > mentioned that an unqua

Re: [PATCH] notes: document behavior of --ref and --notes DWIMery

2015-09-22 Thread Junio C Hamano
Jacob Keller writes: > From: Jacob Keller > > The --notes and --ref parameter for selecting which notes ref to operate > on are based off of expand_notes_ref functionality. The documentation > mentioned that an unqualified ref argument would be taken as under > `refs/notes/`. However, this does

[PATCH] notes: document behavior of --ref and --notes DWIMery

2015-09-22 Thread Jacob Keller
From: Jacob Keller The --notes and --ref parameter for selecting which notes ref to operate on are based off of expand_notes_ref functionality. The documentation mentioned that an unqualified ref argument would be taken as under `refs/notes/`. However, this does not clearly indicate that `refs/he