From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Titus Rwantare" <titusr@google.com>
Cc: qemu-arm@nongnu.org, minyard@acm.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 0/8] PMBus fixes and new functions
Date: Tue, 24 Oct 2023 13:50:20 +0200 [thread overview]
Message-ID: <c87866ad-568b-1917-7617-c63b137a196a@linaro.org> (raw)
In-Reply-To: <87zg082twp.fsf@linaro.org>
On 24/10/23 12:06, Alex Bennée wrote:
> A pull request is really just a GPG signed tag that you push to a repo.
> You can use the existing git tooling to create the cover letter for it.
>
> I've included my exact steps at the end of the email but really it comes
> down to:
>
> git tag --sign your-pr-tag
> git push your-pr-tag
> git format-patch <series details>
> git request-pull origin/master your_repo_details your-pr-tag
>
> and finally
>
> git send-email
>
> My personal exact steps are integrated with my editor but are:
> 8 Preparing a QEMU Pull Request
> ═══════════════════════════════
> 9 And send the pull request
> ═══════════════════════════
For these steps I just do:
$ git publish -b origin/master \
--pull-request --sign-pull --keyid=0xMYKEY
which uses .gitpublish from commit 08bb160e02,
calling get_maintainer.pl for each patch.
Using GSuite, I also have in ~/.gitconfig:
[sendemail]
smtpServer = smtp.gmail.com
smtpBatchSize = 1
smtpReloginDelay = 3
next prev parent reply other threads:[~2023-10-24 11:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 18:08 [PATCH v3 0/8] PMBus fixes and new functions Titus Rwantare
2023-10-23 18:08 ` [PATCH v3 1/8] hw/i2c: pmbus add support for block receive Titus Rwantare
2023-10-23 18:08 ` [PATCH v3 2/8] hw/i2c: pmbus: add vout mode bitfields Titus Rwantare
2023-10-23 18:08 ` [PATCH v3 3/8] hw/i2c: pmbus: add fan support Titus Rwantare
2023-10-23 18:08 ` [PATCH v3 4/8] hw/i2c: pmbus: add VCAP register Titus Rwantare
2023-10-23 18:08 ` [PATCH v3 5/8] hw/sensor: add ADM1266 device model Titus Rwantare
2023-10-23 18:08 ` [PATCH v3 6/8] tests/qtest: add tests for ADM1266 Titus Rwantare
2023-10-23 18:08 ` [PATCH v3 7/8] hw/i2c: pmbus: immediately clear faults on request Titus Rwantare
2023-10-23 18:08 ` [PATCH v3 8/8] hw/i2c: pmbus: reset page register for out of range reads Titus Rwantare
2023-10-23 19:10 ` [PATCH v3 0/8] PMBus fixes and new functions Alex Bennée
2023-10-23 23:53 ` Titus Rwantare
2023-10-24 10:06 ` Alex Bennée
2023-10-24 11:50 ` Philippe Mathieu-Daudé [this message]
2023-10-24 16:07 ` Titus Rwantare
2023-10-25 5:56 ` Philippe Mathieu-Daudé
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=c87866ad-568b-1917-7617-c63b137a196a@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=minyard@acm.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=titusr@google.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).