From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
To: Albert Esteve <aesteve@redhat.com>
Cc: virtio-comment@lists.linux.dev
Subject: Re: [PATCH] git-publish: add profile
Date: Wed, 5 Mar 2025 10:51:06 +0100 [thread overview]
Message-ID: <Z8geil7uaB4UAF7m@fedora> (raw)
In-Reply-To: <CADSE00JHFcsg2vHVOymDd9pawbGWPiBOpZ1guRivAOOOK33xKQ@mail.gmail.com>
On Wed, Mar 05, 2025 at 09:04:59AM +0100, Albert Esteve wrote:
> On Tue, Mar 4, 2025 at 7:47 PM Matias Ezequiel Vara Larsen
> <mvaralar@redhat.com> wrote:
> >
> > Add git-publish profile and document how to use it.
> >
> > Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
> > ---
> > .gitpublish | 3 +++
> > README.md | 9 +++++++++
> > 2 files changed, 12 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"]
> > +base = master
> > +to = virtio-comment@lists.linux.dev
> > diff --git a/README.md b/README.md
> > index c06caf6..39f22d4 100644
> > --- a/README.md
> > +++ b/README.md
> > @@ -110,6 +110,15 @@ 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 git-publisher to submit a patch. The procedure is the following:
>
> s/git-publisher/git-publish/ ?
>
Thanks.
> Maybe even worth adding a link to the project repository?
> ```
> \href{https://github.com/stefanha/git-publish}{git-publish}
> ```
I will add the link to the project.
> Especially since you need to install and set up the tool beforehand,
> so it is nice to have the link pointing to the project documentation.
>
> > +<code>
> > +git checkout master -b my-feature<br>
> > +# work on new commits, add your 'Signed-off-by' lines to each<br>
> > +git publish<br>
>
> The first run (unless you pre-configure your profile in the project
> git config) needs to specify the recipient (with --to) and and cc's.
> I'd add at least the `--to` to the example.
The patch includes a gitpublish profile to avoid configuring the `to`
email. Maybe I can add that the goal of using gitpublish is to simplify
the steps above.
>
> > +... 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
> >
> >
>
prev parent reply other threads:[~2025-03-05 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 16:11 [PATCH] git-publish: add profile Matias Ezequiel Vara Larsen
2025-03-05 8:04 ` Albert Esteve
2025-03-05 8:21 ` Stefano Garzarella
2025-03-05 9:56 ` Matias Ezequiel Vara Larsen
2025-03-05 9:51 ` Matias Ezequiel Vara Larsen [this message]
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=Z8geil7uaB4UAF7m@fedora \
--to=mvaralar@redhat.com \
--cc=aesteve@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.