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

Re: Possible bug: --ext-diff ignored with --cc in git log

From
Jeff King <peff@peff.net>
Date
Mar 11, 2016, 19:45 UTC
Message-ID
<20160311194518.GA1269@sigill.intra.peff.net>
In-Reply-To
<xmqqr3fgal3j.fsf@gitster.mtv.corp.google.com>
On Fri, Mar 11, 2016 at 11:08:32AM -0800, Junio C Hamano wrote:
Show 22 quoted lines
> Jeff King <peff@peff.net> writes:
> 
> >> It happens that the above is fairly easily doable with today's Git
> >> without any modification.  Here is how.
> >> [...]
> >
> > I think an even easier way is:
> >
> >   git log --cc --raw
> >
> > I know that is somewhat beside the point you are making, which is how we
> > should handle "--cc" with ext-diff. But I would much rather have us
> > show nothing for that case, and let the user turn on "--raw", than to
> > invent a diff-looking format that does not actually represent the file
> > contents.
> 
> Sorry, but I am not sure where you are trying to go with this.
> 
> I understand that the original issue was that Vadim wants to
> suppress reams of differences for _some_ paths but still wants to
> benefit from the textual summarized diff for all the other paths.
> Giving "--raw" would be global, and would affect other paths, no?

Ah, sorry, I thought the problem was the opposite: that there was no output for ext-diff paths, and we needed to add something back in. Doing "--raw" is a much easier way than textconv of the "add back in" part, but it does not suppress the ordinary combined diff.

-Peff
Previous: Junio C HamanoNext: Vadim Zeitlin
Message 7 of 8 in “Possible bug: --ext-diff ignored with --cc in git log”
  1. Vadim ZeitlinMar 9, 2016
  2. Junio C HamanoMar 10, 2016
  3. Re[2]: Possible bug: --ext-diff ignored with --cc in git logVadim Zeitlin, Mar 11, 2016
  4. Junio C HamanoMar 11, 2016
  5. Jeff KingMar 11, 2016
  6. Junio C HamanoMar 11, 2016
  7. Jeff KingMar 11, 2016
  8. Re[2]: Possible bug: --ext-diff ignored with --cc in git logVadim Zeitlin, Mar 12, 2016

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.