"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.
>
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
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
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
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
5 matches
Mail list logo