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

Re: git rebase: unexpected conflict

From
MTMichael S. Tsirkin <mst@mellanox.co.il>
Date
Feb 8, 2007, 13:39 UTC
Message-ID
<20070208133921.GB20183@mellanox.co.il>
In-Reply-To
<7vired64tp.fsf@assigned-by-dhcp.cox.net>
Show 19 quoted lines
> Quoting Junio C Hamano <junkio@cox.net>:
> Subject: Re: git rebase: unexpected conflict
> 
> "Michael S. Tsirkin" <mst@mellanox.co.il> writes:
> 
> >> > git-show can not limit its output to just the part of patch
> >> > that affects the list of files I give, the way git-diff can.
> >> > Would such an extension be a good idea?
> >> 
> >> It is a good idea and I think it is implemented.
> >> 
> >> 	$ git-show <commit>... --- <paths>
> >
> > Yes, this works. But this seems undocumented. Right?
> 
> Somehow I think I saw Linus's answer to this exact topic a few
> hours ago.
> 
> This manual page describes only the most frequently used options.

Yes but Linus discussed git-log, which is both complete and correct. Unlike git-log, the man page foor git-show is correct but incomplete: It does say

> This manual page describes only the most frequently used options.

However where git-log man page says: ----- The command takes options applicable to the git-rev-list(1) command to control what is shown and how, and options applicable to the git-diff-tree(1) commands to control how the change each commit introduces are shown. -----

man git-show says nothing of the kind.
-------------------------------------------------------------------
Junio, is the following patch correct?
Signed-off-by: Michael S. Tsirkin <mst@mellanox.co.il>
---
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index b802946..361eaec 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -16,7 +16,7 @@ Shows the commit logs.
 
 The command takes options applicable to the gitlink:git-rev-list[1]
 command to control what is shown and how, and options applicable to
-the gitlink:git-diff-tree[1] commands to control how the change
+the gitlink:git-diff-tree[1] commands to control how the changes
 each commit introduces are shown.
 
 This manual page describes only the most frequently used options.
diff --git a/Documentation/git-show.txt b/Documentation/git-show.txt
index 9051951..f56f164 100644
--- a/Documentation/git-show.txt
+++ b/Documentation/git-show.txt
@@ -25,6 +25,9 @@ with \--name-only).
 
 For plain blobs, it shows the plain contents.
 
+The command takes options applicable to the gitlink:git-diff-tree[1] command to
+control how the changes the commit introduces are shown.
+
 This manual page describes only the most frequently used options.
 
 
-- 
MST
Previous: Junio C HamanoNext: Junio C Hamano
Message 11 of 16 in “git rebase: unexpected conflict”
  1. Michael S. TsirkinFeb 4, 2007
  2. Jakub NarebskiFeb 4, 2007
  3. Michael S. TsirkinFeb 4, 2007
  4. Junio C HamanoFeb 7, 2007
  5. Michael S. TsirkinFeb 7, 2007
  6. Junio C HamanoFeb 7, 2007
  7. Michael S. TsirkinFeb 7, 2007
  8. Junio C HamanoFeb 7, 2007
  9. Michael S. TsirkinFeb 7, 2007
  10. Junio C HamanoFeb 7, 2007
  11. Michael S. TsirkinFeb 8, 2007
  12. Junio C HamanoFeb 8, 2007
  13. Michael S. TsirkinFeb 8, 2007
  14. Michael S. TsirkinFeb 9, 2007
  15. Linus TorvaldsFeb 7, 2007
  16. Linus TorvaldsFeb 7, 2007

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.