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

Re: Potential bug: truncated diff output

From
David Kastrup <dak@gnu.org>
Date
Jan 16, 2014, 07:04 UTC
Message-ID
<87ha944dcb.fsf@fencepost.gnu.org>
In-Reply-To
<52D78244.7020406@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> writes:
Show 13 quoted lines
> Am 1/16/2014 7:19, schrieb Misha Penkov:
>> I have a file in a git repo. It has changed during the last two
>> commits. I want to see the changes made in these two commits. The
>> following command should work:
>> 
>>     git diff HEAD^^
>
> Here, you revert the change...
>
> ... that you made here.
>
> Unsurprisingly, the net effect is no change in that area -- and git diff
> tells you exactly that.

Looks like I should have looked into the diffs before making my guess about what happened.

-- 
David Kastrup
Previous: Johannes SixtNext: Misha Penkov
Message 4 of 5 in “Potential bug: truncated diff output”
  1. Misha PenkovJan 16, 2014
  2. David KastrupJan 16, 2014
  3. Johannes SixtJan 16, 2014
  4. David KastrupJan 16, 2014
  5. Misha PenkovJan 16, 2014

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.