All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
	Stefan Weil <sw@weilnetz.de>
Subject: Re: [PATCH] mailmap: Fix Stefan Weil author email again
Date: Tue, 2 Jan 2024 05:10:21 -0500	[thread overview]
Message-ID: <20240102101021.GA423238@fedora> (raw)
In-Reply-To: <9733fe6c-d9ea-4945-ba06-8d23890f22c7@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]

On Wed, Dec 27, 2023 at 10:21:26AM +0100, Philippe Mathieu-Daudé wrote:
> On 27/12/23 10:12, Philippe Mathieu-Daudé wrote:
> > On 27/12/23 10:09, Michael Tokarev wrote:
> > > 27.12.2023 11:59, Philippe Mathieu-Daudé:
> > > > Commit 5204b499a6 ("mailmap: Fix Stefan Weil author email")
> > > > corrected authorship for patch received at qemu-devel@nongnu.org,
> > > > correct now for patch received at qemu-trivial@nongnu.org.
> > > > 
> > > > Fixes: d819fc9516 ("virtio-blk: Fix potential nullptr read access")
> > > 
> > > Do you think a single commit warrants an entry in mailmap?
> > 
> > If I cared enough to write and post a patch, I suppose so...
> > 
> > In the past the only limitation was whether someone was willing
> > to do the work and send a patch, not the size of the .mailmap
> > file.
> 
> A more useful use of our time would be a git pre-merge hook on
> our CI, but that won't work because PR aren't merged on the CI
> but externally, and the final commit is pushed.
> 
> The only place I can think of to automate that is to have a
> script on the maintainer side. Remembering Peter had a such
> script, I found a reference in the list:
> https://git.linaro.org/people/pmaydell/misc-scripts.git/commit/?id=f9a317392e8
> 
> Stefan, do you mind using Peter's script for your merges?

Yes, in future releases. Peter is handling the QEMU 9.0 release so I
will not be merging pull requests for the time being.

Thanks,
Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2024-01-02 10:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27  8:59 [PATCH] mailmap: Fix Stefan Weil author email again Philippe Mathieu-Daudé
2023-12-27  9:09 ` Michael Tokarev
2023-12-27  9:12   ` Philippe Mathieu-Daudé
2023-12-27  9:21     ` Philippe Mathieu-Daudé
2023-12-27  9:48       ` Michael Tokarev
2024-01-02 10:10       ` Stefan Hajnoczi [this message]
2023-12-27 19:03     ` Stefan Weil
2023-12-27 19:03       ` Stefan Weil via

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=20240102101021.GA423238@fedora \
    --to=stefanha@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=sw@weilnetz.de \
    /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.