From: Stefan Hajnoczi <stefanha@redhat.com>
To: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
Cc: virtio-comment@lists.linux.dev, aesteve@redhat.com, sgarzare@redhat.com
Subject: Re: [PATCH v3] git-publish: add profile
Date: Thu, 6 Mar 2025 13:22:31 +0800 [thread overview]
Message-ID: <20250306052231.GE303194@fedora> (raw)
In-Reply-To: <20250305164546.1484029-1-mvaralar@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2223 bytes --]
On Wed, Mar 05, 2025 at 05:45:46PM +0100, Matias Ezequiel Vara Larsen wrote:
> Add git-publish profile and document how to use it.
>
> Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
> ---
> v2 -> v3:
> * remove uppercase and the line split and use italic
> v1 -> v2:
> * add link to git-publish
> * document that the project contains a profile already
> ---
> .gitpublish | 3 +++
> README.md | 15 +++++++++++++++
> 2 files changed, 18 insertions(+)
> create mode 100644 .gitpublish
>
> diff --git a/.gitpublish b/.gitpublish
> new file mode 100644
> index 0000000..d412896
> --- /dev/null
> +++ b/.gitpublish
> @@ -0,0 +1,3 @@
> +[gitpublishprofile "default"]
Great, this will make it easier to send spec changes!
> +base = master
> +to = virtio-comment@lists.linux.dev
From https://github.com/oasis-tcs/virtio-spec?tab=readme-ov-file:
When not to use the virtio-comment mailing list:
questions and change proposals for Virtio drivers and devices
implementing the specification. (please use the virtio-dev mailing
list for this).
This also matches what I found in my .git/config where gitpublishto was
set to virtio-dev rather than virtio-comment.
> diff --git a/README.md b/README.md
> index c06caf6..b521978 100644
> --- a/README.md
> +++ b/README.md
> @@ -110,6 +110,21 @@ git format-patch -o proposal1/ HEAD~1..<br>
> git send-email --to=virtio-comment@lists.linux.dev proposal1/0001-*
> </code>
>
> +<dl>Optionally, you can use <a
> +href="https://github.com/stefanha/git-publish">git-publish</a> to submit a
> +patch. This project already contains a <em>git-publish</em> profile that will
> +configure some fields, e.g., <em>To</em> field with the right address. After you have
> +installed <em>git-publish</em>, the procedure is the following:
> +
> +<code>
> +<p>
> +git checkout master -b my-feature<br>
> +# work on new commits, add your 'Signed-off-by' lines to each<br>
> +git publish<br>
> +# more work, rebase on master, ...<br>
> +git publish # will send a v2<br>
> +</code>
> +</dl>
> <dl>
> <dt>When to use the virtio-comment mailing list:</dt>
> <dd>
> --
> 2.42.0
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-03-06 5:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 16:45 [PATCH v3] git-publish: add profile Matias Ezequiel Vara Larsen
2025-03-06 5:22 ` Stefan Hajnoczi [this message]
2025-03-06 9:40 ` Matias Ezequiel Vara Larsen
2025-03-06 9:58 ` Stefano Garzarella
2025-03-06 10:43 ` Albert Esteve
2025-03-06 10:51 ` Stefano Garzarella
2025-03-06 16:13 ` Albert Esteve
2025-03-11 2:17 ` Stefan Hajnoczi
2025-03-06 10:04 ` Stefano Garzarella
2025-03-06 16:15 ` Albert Esteve
2025-03-10 13:21 ` Cornelia Huck
2025-09-23 8:09 ` Matias Ezequiel Vara Larsen
2025-09-23 12:14 ` Parav Pandit
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=20250306052231.GE303194@fedora \
--to=stefanha@redhat.com \
--cc=aesteve@redhat.com \
--cc=mvaralar@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtio-comment@lists.linux.dev \
/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.