From: Junio C Hamano <gitster@pobox.com>
To: Rob Linden <rlinden@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: problem with parsing of patch files for patch-id
Date: Fri, 21 Jun 2024 10:05:23 -0700 [thread overview]
Message-ID: <xmqqbk3uns4s.fsf@gitster.g> (raw)
In-Reply-To: <CAP0H_AEd1jFNB_dO=HRjwEUKzFqnjntss_1wskKU6hE1VmBs+A@mail.gmail.com> (Rob Linden's message of "Fri, 21 Jun 2024 12:33:10 +0200")
Rob Linden <rlinden@redhat.com> writes:
> This patch (also attached) fixes it by only considering commit hashes
> in a "From xxxxx..." line:
If I am not mistaken, "git patch-id" was designed to read from
git rev-list ... commit range ... | git diff-tree --stdin -p
where we see
9005149a4a77e2d3409c6127bf4fd1a0893c3495
diff --git a/path b/path
index ...
... patch text here ...
so I would suspect that limiting the commit object names only to
those that follow "From " (i.e. the format-patch output or output
with the "--format=email" option) would break existing use cases big
time.
next prev parent reply other threads:[~2024-06-21 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 10:33 problem with parsing of patch files for patch-id Rob Linden
2024-06-21 17:05 ` Junio C Hamano [this message]
2024-06-21 18:15 ` Rob Linden
2024-07-13 16:25 ` Junio C Hamano
2024-06-21 18:53 ` 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=xmqqbk3uns4s.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rlinden@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.