[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 2/7] docs/devel: add git-publish for patch submitting
From: |
Daniel P . Berrangé |
Subject: |
Re: [PATCH 2/7] docs/devel: add git-publish for patch submitting |
Date: |
Wed, 20 Nov 2024 10:01:27 +0000 |
User-agent: |
Mutt/2.2.12 (2023-09-09) |
On Wed, Nov 20, 2024 at 09:51:27AM +0000, Alex Bennée wrote:
>
> I still send pull requests by hand:
>
> git send-email --confirm=never --quiet ${mailto} ${series}.pull/*
>
> but thats probably because I haven't figured out the steps for git
> publish to do that.
A one-time setup task is to tell it what you preferred git remote is.
I use "gitlab" as the name of my personal gitlab fork of QEMU, so
$ git config remote.pushDefault gitlab
With that one-time setup task, sending a pull rquest needs nothing more
than adding '--pull' to the git-publish cli. It'll trigger signing of
the tag, so be sure you have your gpg key available, and then push both
the branch and signed tag to your git remote, and send emails in its
normal way.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
- Re: [PATCH 3/7] docs/devel: add b4 for patch retrieval, (continued)
[PATCH 2/7] docs/devel: add git-publish for patch submitting, Pierrick Bouvier, 2024/11/18
Re: [PATCH 2/7] docs/devel: add git-publish for patch submitting, Daniel P . Berrangé, 2024/11/19
[PATCH 4/7] docs/devel: add information on how to setup build environments, Pierrick Bouvier, 2024/11/18
[PATCH 1/7] docs/devel: remove dead video link for sourcehut submit process, Pierrick Bouvier, 2024/11/18
[PATCH 6/7] docs: add a glossary, Pierrick Bouvier, 2024/11/18