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

Re: [PATCH] sequencer.c: abbreviate hashs placed in the middle of messages

From: Ralf Thielow <hidden>
Date: 2016-06-15 23:04:41

Junio C Hamano [off-list ref] wrote:
And shortening the output feels to me a more expedient thing to do
because we do not have to analyse the ramification of possible
information loss (your "It has value since...").  If we analyse the
issue well, we might realize that there is little point in showing
the commit object name in hexadecimal, be it in full or in shortened
form.

If the proposal were to parrot what the user typed on the command
line, e.g. one of these (or their rephrased versions)

        error: commit 'next' is a merge but no -m option was given.
        error: no -m option was given to pick a merge 'next'.

against the above example, then I would say that would be an
improvement, but that is not what is being discussed, so...
Commits to be merged don't have to be branches.

OK. So let's stay with 40 character hash in the messages.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help