Junio C Hamano <[email protected]> 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
