From: Will Deacon <will@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@kernel.org, Jason Gunthorpe <jgg@nvidia.com>,
Nicolin Chen <nicolinc@nvidia.com>
Subject: Re: [PATCH v2 0/2] b4: ty: Fix incorrect patch/commit association
Date: Thu, 2 May 2024 10:23:54 +0100 [thread overview]
Message-ID: <20240502092354.GA16551@willie-the-truck> (raw)
In-Reply-To: <171459859217.935458.14461888310866914252.b4-ty@linuxfoundation.org>
On Wed, May 01, 2024 at 05:23:12PM -0400, Konstantin Ryabitsev wrote:
>
> On Mon, 04 Mar 2024 13:42:39 +0000, Will Deacon wrote:
> > It's me again. This time I fixed my git configuration so that the
> > authorship is correct and matches the S-o-B line. That's the only change
> > since the v1 I sent on Friday.
> >
> > Enjoy!
> >
> > Will
> >
> > [...]
>
> Applied, thanks!
>
> [1/2] ty: Try subject matching for every commit before using trackers
> commit: 47bd55d3182d875802700670270f5ee0877a8d5d
> [2/2] ty: Remove unused 'matches' variable
> commit: dced92071d2135ccbec521cb4face63cafcdc407
You applied these already (with different SHAs), I think:
https://lore.kernel.org/r/170958794467.8875.12454526353405240108.b4-ty@linuxfoundation.org
So I'm not sure what's happened here :/
Will
next prev parent reply other threads:[~2024-05-02 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 13:42 [PATCH v2 0/2] b4: ty: Fix incorrect patch/commit association Will Deacon
2024-03-04 13:42 ` [PATCH v2 1/2] ty: Try subject matching for every commit before using trackers Will Deacon
2024-03-04 13:42 ` [PATCH v2 2/2] ty: Remove unused 'matches' variable Will Deacon
2024-03-04 21:32 ` [PATCH v2 0/2] b4: ty: Fix incorrect patch/commit association Konstantin Ryabitsev
2024-05-01 21:23 ` Konstantin Ryabitsev
2024-05-02 9:23 ` Will Deacon [this message]
2024-05-02 18:31 ` Konstantin Ryabitsev
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=20240502092354.GA16551@willie-the-truck \
--to=will@kernel.org \
--cc=jgg@nvidia.com \
--cc=konstantin@linuxfoundation.org \
--cc=nicolinc@nvidia.com \
--cc=tools@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).