kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mail@beyermatthias.de (Matthias Beyer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Workflow improvements when sending patches with format-patch && send-email ?
Date: Sun, 24 Aug 2014 13:27:13 +0200	[thread overview]
Message-ID: <20140824112713.GR9303@fu.fritz.box> (raw)

Hi,

I have a problem related to my workflow when patching kernel sources.
What I do by now, when sending patches:

    scripts/get_maintainer.pl --file my/patched/file.c

    git format-patch -s -n --cover-letter
    # and then appending _every single mail from the get_maintainer.pl
    # call with either --to or --cc
    # and the commit range

    git send-email --no-chain-reply-to
    # and then appending _every single mail from the get_maintainer.pl
    # call with either --to or --cc
    ./00*

The second step is mainly copy-paste from the format-patch call, but I
guess you already notice my issue: I have to "hand-copy" every email
address from the get_maintainer.pl call.

I also send my patches to two persons which do not get listed from the
get_maintainer.pl call most of the time, plus I do not send my patches
to the LKML directly (but the driverdev ML).

I consider this hard work, especially when having a lot of _small_
patchsets, as I do this for every single patchset and it really annoys
me.

Are there tools somewhere to simplify these steps? Something like

    "generate & send patches from bla-blubb...foobazbar"

and then it:

    1) Gets mailaddrs from get_maintainer.pl
    2) lets me add additional and delete receivers
    3) asks me which one gets a --to and which one a --cc
    4) generates the patches with format-patch
    5) (optionally) runs checkpatch.pl on it
    6) sends the patches with send-email after confirmation

Are there some tools out there? Or how do you guys do this? Or are
there tweaks built-in in git that I don't know yet?

-- 
Mit freundlichen Gr??en,
Kind regards,
Matthias Beyer

Proudly sent with mutt.
Happily signed with gnupg.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140824/d9d6c8db/attachment.bin 

             reply	other threads:[~2014-08-24 11:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-24 11:27 Matthias Beyer [this message]
2014-08-26 19:39 ` Workflow improvements when sending patches with format-patch && send-email ? Laurent Navet
2014-08-27  8:28 ` Bjørn Mork

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=20140824112713.GR9303@fu.fritz.box \
    --to=mail@beyermatthias.de \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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).