Thread (5 messages) flat view 5 messages, 3 authors, 2016-06-15

Re: [RFD] Notes are independent: proposal for new notes implementation

From: Avery Pennarun <hidden>
Date: 2016-06-15 22:48:12

2010/2/9 Jakub Narebski [off-list ref]:
But
what if the answer was to change implementation, decoupling history of
notes from each other, and keeping history of each note separate.
Congratulations, you've re-invented CVS! :)

Seriously though, I'm not sure what problems this solved.  Notes that
are related to each other can (and perhaps should) be in the same
notes commit history; notes that are not related to each other can
exist in separate histories with their own ref.
This means for example that if in repository A somebody annotated
commits foo and bar creating notes in this order, and in repository B
somebody annotated bar and foo (creating notes in reverse order), then
merging those changes would require generating merge commit even if
those notes are identical.
That's a feature; now you have the true history of your notes, which
is good for all the same reasons it's good in git.

Of course this whole line of reasoning could lead to questions like
"can I rebase my notes history?" and "what about rebase -i" and "can I
maintain a notes patch queue" and so on.

Have fun,

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