[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]
From: Nicolas Sebrecht
Date: Friday, July 9, 2010 - 1:27 pm

Signed-off-by: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
---
 merge-recursive.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/merge-recursive.c b/merge-recursive.c
index 856e98c..fb6aa4a 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -1214,7 +1214,7 @@ int merge_trees(struct merge_options *o,
 	}
 
 	if (sha_eq(common->object.sha1, merge->object.sha1)) {
-		output(o, 0, "Already uptodate!");
+		output(o, 0, "Already up-to-date!");
 		*result = head;
 		return 1;
 	}
-- 
1.7.2.rc2.194.g494e9.dirty

--
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)
[PATCH v4 2/2] merge-recursive: use "up-to-date" instead o ..., Nicolas Sebrecht, (Fri Jul 9, 1:27 pm)