Re: [PATCH 2/7] docs/devel: add git-publish for patch submitting

[Pierrick Bouvier]

On 11/19/24 00:41, Marcin Juszkiewicz wrote:
> W dniu 18.11.2024 o 18:23, Pierrick Bouvier pisze:
> > Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
> > ---
> >    docs/devel/submitting-a-patch.rst | 14 ++++++++++++++
> >    1 file changed, 14 insertions(+)
> >
> > diff --git a/docs/devel/submitting-a-patch.rst 
> > b/docs/devel/submitting-a-patch.rst
> > index 349c32ee3a9..953682f20cb 100644
> > --- a/docs/devel/submitting-a-patch.rst
> > +++ b/docs/devel/submitting-a-patch.rst
> > @@ -237,6 +237,20 @@ attachments can be used as a last resort on a first-time 
> > submission.
> >    
> >    .. _if_you_cannot_send_patch_emails:
> >    
> > +Use git-publish
> > +~~~~~~~~~~~~~~~
> > +
> > +If you already configured git send-email, you can simply use `git-publish
> > +<https://github.com/stefanha/git-publish>`__ to send series.
> > +
> > +::
> > +
> > +    $ git checkout master -b my-feature
> > +    $ # work on new commits, add your 'Signed-off-by' lines to each
> > +    $ git publish
> > +    $ ... more work, rebase on master, ...
> > +    $ git publish # will send a v2
>
> You recommend 'b4 shazam' in 3/7 patch so why not here? Both 'b4' and
> 'git-publish' seem to do same stuff - handle patch series and send them
> upstream.

Are you using b4 for your QEMU contributions?

When I started working on QEMU, I tried it before git-publish and had an 
error when trying to send my series. I don't remember exactly what it 
was, but something related to finding the reviewers for a given commit. 
When I asked, team members pointed me towards git-publish.

> b4 allows to keep To/Cc emails inside of cover letter which makes it
> easy to not miss anyone needed.

git-publish works pretty well for me, and does what you expect (keep 
your cover letter/cc and track your versions).