git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 1/2] checkout: accord documentation to what git does

From
NSNicolas Sebrecht <nicolas.s.dev@gmx.fr>
Date
Jul 9, 2010, 20:27 UTC
Message-ID
<33e9dcc468b1e1ed18a180046f5d4c135921c7ab.1278707023.git.nicolas.s.dev@gmx.fr>
In-Reply-To
<7vd3uystsh.fsf@alter.siamese.dyndns.org>
Signed-off-by: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
---
The 07/07/10, Junio C Hamano wrote:
Show 18 quoted lines
> Nicolas Sebrecht <nicolas.s.dev@gmx.fr> writes:
> > Signed-off-by: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
> > ---
> >
> > The 07/07/10, Junio C Hamano wrote:
> >
> >> 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 ;-)
Doh! You said in this commit that
	"If you do not see something wrong with this output, your brain has already
	been rotten with use of git for too long a time."
but I claim the right to be rotten in much more ways. :-)
 Documentation/git-checkout.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt
index 261dd90..1bacd2e 100644
--- a/Documentation/git-checkout.txt
+++ b/Documentation/git-checkout.txt
@@ -263,7 +263,7 @@ the above checkout would fail like this:
 +
 ------------
 $ git checkout mytopic
-fatal: Entry 'frotz' not uptodate. Cannot merge.
+error: You have local changes to 'frotz'; not switching branches.
 ------------
 +
 You can give the `-m` flag to the command, which would try a
-- 
1.7.2.rc2.194.g494e9.dirty
Previous: Junio C HamanoNext: Junio C Hamano
Message 11 of 16 in “messages confusing”
  1. Nicolas SebrechtJul 6, 2010
  2. Wincent ColaiutaJul 6, 2010
  3. use "up-to-date" in messages instead of "uptodate" for consistencyNicolas Sebrecht, Jul 6, 2010
  4. Ævar Arnfjörð BjarmasonJul 6, 2010
  5. use "up-to-date" instead of "uptodate" for consistencyNicolas Sebrecht, Jul 6, 2010
  6. Junio C HamanoJul 7, 2010
  7. Re: use "up-to-date" instead of "uptodate" for consistencyNicolas Sebrecht, Jul 7, 2010
  8. Junio C HamanoJul 7, 2010
  9. merge-recursive: use "up-to-date" instead of "uptodate" in error message for consistencyNicolas Sebrecht, Jul 7, 2010
  10. Junio C HamanoJul 8, 2010
  11. 1/2 checkout: accord documentation to what git doesNicolas Sebrecht, Jul 9, 2010
  12. Junio C HamanoJul 10, 2010
  13. 2/2 merge-recursive: use "up-to-date" instead of "uptodate" in error message for consistencyNicolas Sebrecht, Jul 9, 2010
  14. Junio C HamanoJul 10, 2010
  15. Junio C HamanoJul 6, 2010
  16. Nicolas SebrechtJul 6, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.