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

Re: [PATCH 3/3] diff-index.txt: update raw output format in examples

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 13, 2022, 18:59 UTC
Message-ID
<xmqqpmjc5r0g.fsf@gitster.g>
In-Reply-To
<af67c33916f5ff29f158f400d6365e6c09e80eea.1655123383.git.gitgitgadget@gmail.com>
"Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 16 quoted lines
> From: Philippe Blain <levraiphilippeblain@gmail.com>
>
> The two examples in the doc for 'git diff-index' were not updated when
> the raw output format was changed in 81e50eabf0 ([PATCH] The diff-raw
> format updates., 2005-05-21) (first example) and in b6d8f309d9 ([PATCH]
> diff-raw format update take #2., 2005-05-23) and 7cb6ac1e4b (diff:
> diff_aligned_abbrev: remove ellipsis after abbreviated SHA-1 value,
> 2017-12-03) (second example).
>
> Update the output, inventing some characters to complete the source
> hash in the second example. Also correct the destination mode in the
> second example, which was wrongly '100664' since the addition of the
> example in c64b9b8860 (Reference documentation for the core git
> commands., 2005-05-05).
>
> Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com>
Thanks.
Previous: Philippe Blain via GitGitGadgetNext: Junio C Hamano
Message 10 of 11 in “Fix a few documentation errors around the raw diff output”
  1. 0/3 Fix a few documentation errors around the raw diff outputPhilippe Blain via GitGitGadget, Jun 13, 2022
  2. 1/3 diff-format.txt: fix ancient copy-paste errorPhilippe Blain via GitGitGadget, Jun 13, 2022
  3. Junio C HamanoJun 13, 2022
  4. Junio C HamanoJun 13, 2022
  5. Philippe BlainJun 14, 2022
  6. 2/3 diff-format.txt: correct misleading wordingPhilippe Blain via GitGitGadget, Jun 13, 2022
  7. Junio C HamanoJun 13, 2022
  8. Philippe BlainJun 14, 2022
  9. 3/3 diff-index.txt: update raw output format in examplesPhilippe Blain via GitGitGadget, Jun 13, 2022
  10. Junio C HamanoJun 13, 2022
  11. Junio C HamanoJun 13, 2022

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.