Re: [PATCHv4 08/12] Teach the notes lookup code to parse notes trees with various fanout schemes

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCHv4 08/12] Teach the notes lookup code to parse notes trees with various fanout schemes

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:47:19

Sverre Rabbelier [off-list ref] writes:
On Thu, Aug 27, 2009 at 18:43, Junio C Hamano[off-list ref] wrote:
quoted
Did you mean "a commit in branch bar referred to a commit in branch foo",
similar to the way the "cherry-picked from X" comment can refer to a
missing commit?
Yes, sorry, I meant referred to in the commit message.
In such a case would you rather want to see the commit itself first, or at
least, commit _and_ notes _together_?

I admit that this all depends on what application the notes are used for,
but I am suffering from lack of imagination to come up with a plausible
scenario in which you would want to look at the notes to that missing
commit first, without getting the commit itself.

Re: [PATCHv4 08/12] Teach the notes lookup code to parse notes trees with various fanout schemes

From: Sverre Rabbelier <hidden>
Date: 2016-06-15 22:47:19

Heya,

On Thu, Aug 27, 2009 at 20:02, Junio C Hamano[off-list ref] wrote:
In such a case would you rather want to see the commit itself first, or at
least, commit _and_ notes _together_?
Assuming you do download all notes, I think it would be nice to be
able to read the note; and since there's no way to download the commit
separately it would require one to guess which head the commit belongs
to and fetch the entire branch...?

-- 
Cheers,

Sverre Rabbelier
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help