Re: [PATCH v4 2/2] merge-recursive: use "up-to-date" instead of "uptodate" in error message for consistency

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Nicolas Sebrecht <nicolas.s.dev@gmx.fr> writes:


Sorry, but the pros-and-cons is not good enough for me to support this
change.  It will break users who have been parsing output with scripts.

We do strongly warn people against relying on Porcelain output, but that
does not mean we are free to change them without having a good reason or
two.  The new spelling won't help the next reader who will find the
message confusing the same way you did a few days ago.

IOW, if we are touching this line anyway, I'd like to make sure we made an
effort to make it less confusing, not just spelled correctly, while we
still have our memory of confusion fresh ;-)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
messages confusing, Nicolas Sebrecht, (Mon Jul 5, 10:35 pm)
Re: messages confusing, Wincent Colaiuta, (Mon Jul 5, 10:53 pm)
Re: messages confusing, Junio C Hamano, (Mon Jul 5, 11:21 pm)
Re: messages confusing, Nicolas Sebrecht, (Tue Jul 6, 1:58 am)
[PATCH 1/2] checkout: accord documentation to what git does, Nicolas Sebrecht, (Fri Jul 9, 1:27 pm)
Re: [PATCH v4 2/2] merge-recursive: use "up-to-date" inste ..., Junio C Hamano, (Fri Jul 9, 5:39 pm)