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

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

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

Possibly related (same subject, not in this thread)

Nicolas Sebrecht [off-list ref] writes:
Signed-off-by: Nicolas Sebrecht <redacted>
---

The 07/07/10, Junio C Hamano wrote:
quoted
The "struct unpack_trees_error_msgs" mechanism was introduced so that we
can change the Porcelain level messages without breaking the plumbing API,
which these messages are part of.  Please see 8ccba00 (unpack-trees: allow
Porcelain to give different error messages, 2008-05-17) and fadd069
(merge-recursive: give less scary messages when merge did not start,
2009-09-07) for backstory.
Oh, thanks. I was unaware of this mechanism and didn't care about what I was
touching.
I suspect that the documentation patch talks about a nonexistent reality.
See 8ccba00 again ;-)
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help