From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Philippe Blain via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] diff-format.txt: fix ancient copy-paste error
Date: Tue, 14 Jun 2022 08:20:57 -0400 [thread overview]
Message-ID: <f6e86c07-0c70-3837-abb2-874d599359b8@gmail.com> (raw)
In-Reply-To: <xmqq35g8772x.fsf@gitster.g>
Hi Junio,
Le 2022-06-13 à 14:26, Junio C Hamano a écrit :
> "Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
>> From: Philippe Blain <levraiphilippeblain@gmail.com>
>>
>> Fix what is probably a copy-paste error dating back all the way to
>> b6d8f309d9 ([PATCH] diff-raw format update take #2., 2005-05-23).
>
> I'll retitle and rewrite the message like so:
>
> diff-format.txt: dst can be 0* SHA-1 when path is deleted, too
>
> "dst" can legitimately be "0\{40\}" for a creation patch, e.g. when
> the stat information is stale, but it falls into "look at work tree"
> case. The original description in b6d8f309 ([PATCH] diff-raw format
> update take #2., 2005-05-23) forgot that deletion also makes the
> "dst" 0* SHA-1.
>
> Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
>
> Thanks.
>
OK, that makes sense. I hadn't thought of the case you are mentioning here
(new file added to the index and then modified).
Thanks,
Philippe.
next prev parent reply other threads:[~2022-06-14 12:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 12:29 [PATCH 0/3] Fix a few documentation errors around the raw diff output Philippe Blain via GitGitGadget
2022-06-13 12:29 ` [PATCH 1/3] diff-format.txt: fix ancient copy-paste error Philippe Blain via GitGitGadget
2022-06-13 18:23 ` Junio C Hamano
2022-06-13 18:26 ` Junio C Hamano
2022-06-14 12:20 ` Philippe Blain [this message]
2022-06-13 12:29 ` [PATCH 2/3] diff-format.txt: correct misleading wording Philippe Blain via GitGitGadget
2022-06-13 18:56 ` Junio C Hamano
2022-06-14 12:31 ` Philippe Blain
2022-06-13 12:29 ` [PATCH 3/3] diff-index.txt: update raw output format in examples Philippe Blain via GitGitGadget
2022-06-13 18:59 ` Junio C Hamano
2022-06-13 18:15 ` [PATCH 0/3] Fix a few documentation errors around the raw diff output Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f6e86c07-0c70-3837-abb2-874d599359b8@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).