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

Re: [PATCH v2] Re: use "up-to-date" instead of "uptodate" for consistency

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

Possibly related (same subject, not in this thread)

Nicolas Sebrecht [off-list ref] writes:
The 06/07/10, Junio C Hamano wrote:
quoted
Nicolas Sebrecht [off-list ref] writes:
quoted
@@ -22,7 +22,7 @@ static struct unpack_trees_error_msgs unpack_plumbing_errors = {
What word do you see before "errors" on the hunk comment line?
So you'd rather not touching it?
Well, "'d rather" is actually too weak a statement.

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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help