From: Greg KH <greg@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
Subject: Re: How to automate checkpatch && get_maintainers && git send-email of commits range?
Date: Fri, 18 Jul 2014 20:40:21 +0000 [thread overview]
Message-ID: <20140718204021.GA7233@kroah.com> (raw)
In-Reply-To: <CANZNk82c8=Ypw_DXDpLZkuvOvjOevccCk70inXOpeKD3h9fnrQ@mail.gmail.com>
On Fri, Jul 18, 2014 at 06:24:15PM +0300, Andrey Utkin wrote:
> 2014-07-18 17:46 GMT+03:00 Benoit Taine <benoit.taine@lip6.fr>:
> > On 18/07/2014 17:38, Andrey Utkin wrote:
> >> Is there script for automated checkpatch.pl && get_maintainers.pl &&
> >> git send-email for range of commits? I see none. Would it be welcome
> >> to submit such one to kernel tree?
>
> > You can use `splitpatch` to split a patch into multiple mails with the
> > correct mailing list and maintainers. It generates a script to
> > chain-send these emails using `cocci-send-email` (a modified version of
> > `git-send-email`).
> >
> > Both are available in the `tools/` directory of coccinelle's
> > distribution <http://coccinelle.lip6.fr/>.
>
> Thank you for this info, but it doesn't match exactly what i seek for.
> I'd like to automate checking and sending exactly of range of git
> commits, or of a set of files generated by git-format-patch.
> I also cannot use cocci-send-email because it doesn't pick To: and Cc:
> lines which i inject into git-format-patch-formatted files. And i
> don't know tools to format the patches in "The original format used by
> Greg Kroah-Hartman's send_lots_of_email.pl script".
> My target should be to
> - check all patches,
> - find set of email addresses to Cc for each patch,
> - send them at once to correct sets of addresses, entering SMTP
> password only once if it is not stored in git-config.
git send-email can do all of the last two things, have you tried it?
As for the format for my old script, I should just delete that logic, I
don't even use it anymore, I just use git send-email.
thanks,m
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to automate checkpatch && get_maintainers && git send-email of commits range?
Date: Fri, 18 Jul 2014 13:40:21 -0700 [thread overview]
Message-ID: <20140718204021.GA7233@kroah.com> (raw)
In-Reply-To: <CANZNk82c8=Ypw_DXDpLZkuvOvjOevccCk70inXOpeKD3h9fnrQ@mail.gmail.com>
On Fri, Jul 18, 2014 at 06:24:15PM +0300, Andrey Utkin wrote:
> 2014-07-18 17:46 GMT+03:00 Benoit Taine <benoit.taine@lip6.fr>:
> > On 18/07/2014 17:38, Andrey Utkin wrote:
> >> Is there script for automated checkpatch.pl && get_maintainers.pl &&
> >> git send-email for range of commits? I see none. Would it be welcome
> >> to submit such one to kernel tree?
>
> > You can use `splitpatch` to split a patch into multiple mails with the
> > correct mailing list and maintainers. It generates a script to
> > chain-send these emails using `cocci-send-email` (a modified version of
> > `git-send-email`).
> >
> > Both are available in the `tools/` directory of coccinelle's
> > distribution <http://coccinelle.lip6.fr/>.
>
> Thank you for this info, but it doesn't match exactly what i seek for.
> I'd like to automate checking and sending exactly of range of git
> commits, or of a set of files generated by git-format-patch.
> I also cannot use cocci-send-email because it doesn't pick To: and Cc:
> lines which i inject into git-format-patch-formatted files. And i
> don't know tools to format the patches in "The original format used by
> Greg Kroah-Hartman's send_lots_of_email.pl script".
> My target should be to
> - check all patches,
> - find set of email addresses to Cc for each patch,
> - send them at once to correct sets of addresses, entering SMTP
> password only once if it is not stored in git-config.
git send-email can do all of the last two things, have you tried it?
As for the format for my old script, I should just delete that logic, I
don't even use it anymore, I just use git send-email.
thanks,m
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Andrey Utkin <andrey.krieger.utkin@gmail.com>
Cc: Benoit Taine <benoit.taine@lip6.fr>,
adobriyan@gmail.com, kernel-janitors@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kernelnewbies@kernelnewbies.org
Subject: Re: How to automate checkpatch && get_maintainers && git send-email of commits range?
Date: Fri, 18 Jul 2014 13:40:21 -0700 [thread overview]
Message-ID: <20140718204021.GA7233@kroah.com> (raw)
In-Reply-To: <CANZNk82c8=Ypw_DXDpLZkuvOvjOevccCk70inXOpeKD3h9fnrQ@mail.gmail.com>
On Fri, Jul 18, 2014 at 06:24:15PM +0300, Andrey Utkin wrote:
> 2014-07-18 17:46 GMT+03:00 Benoit Taine <benoit.taine@lip6.fr>:
> > On 18/07/2014 17:38, Andrey Utkin wrote:
> >> Is there script for automated checkpatch.pl && get_maintainers.pl &&
> >> git send-email for range of commits? I see none. Would it be welcome
> >> to submit such one to kernel tree?
>
> > You can use `splitpatch` to split a patch into multiple mails with the
> > correct mailing list and maintainers. It generates a script to
> > chain-send these emails using `cocci-send-email` (a modified version of
> > `git-send-email`).
> >
> > Both are available in the `tools/` directory of coccinelle's
> > distribution <http://coccinelle.lip6.fr/>.
>
> Thank you for this info, but it doesn't match exactly what i seek for.
> I'd like to automate checking and sending exactly of range of git
> commits, or of a set of files generated by git-format-patch.
> I also cannot use cocci-send-email because it doesn't pick To: and Cc:
> lines which i inject into git-format-patch-formatted files. And i
> don't know tools to format the patches in "The original format used by
> Greg Kroah-Hartman's send_lots_of_email.pl script".
> My target should be to
> - check all patches,
> - find set of email addresses to Cc for each patch,
> - send them at once to correct sets of addresses, entering SMTP
> password only once if it is not stored in git-config.
git send-email can do all of the last two things, have you tried it?
As for the format for my old script, I should just delete that logic, I
don't even use it anymore, I just use git send-email.
thanks,m
greg k-h
next prev parent reply other threads:[~2014-07-18 20:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 14:38 How to automate checkpatch && get_maintainers && git send-email of commits range? Andrey Utkin
2014-07-18 14:38 ` Andrey Utkin
2014-07-18 14:38 ` Andrey Utkin
2014-07-18 14:46 ` Benoit Taine
2014-07-18 14:46 ` Benoit Taine
2014-07-18 15:24 ` Andrey Utkin
2014-07-18 15:24 ` Andrey Utkin
2014-07-18 15:24 ` Andrey Utkin
2014-07-18 20:40 ` Greg KH [this message]
2014-07-18 20:40 ` Greg KH
2014-07-18 20:40 ` Greg KH
2014-07-18 22:22 ` Theodore Ts'o
2014-07-18 22:22 ` Theodore Ts'o
2014-07-18 22:22 ` Theodore Ts'o
2014-07-18 22:47 ` Joe Perches
2014-07-18 22:47 ` Joe Perches
2014-07-18 22:47 ` Joe Perches
2014-07-18 22:50 ` Joe Perches
2014-07-18 22:50 ` Joe Perches
2014-07-18 22:50 ` Joe Perches
2014-07-19 1:31 ` Steven Rostedt
2014-07-19 1:31 ` Steven Rostedt
2014-07-19 1:31 ` Steven Rostedt
2014-07-19 3:35 ` Hillf Danton
2014-07-19 3:35 ` Hillf Danton
2014-07-19 3:35 ` Hillf Danton
2014-07-19 4:05 ` Nick Krause
2014-07-19 4:05 ` Nick Krause
2014-07-19 4:05 ` Nick Krause
2014-07-20 22:23 ` Dave Chinner
2014-07-20 22:23 ` Dave Chinner
2014-07-20 22:23 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2014-07-18 14:55 Alexey Dobriyan
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=20140718204021.GA7233@kroah.com \
--to=greg@kroah.com \
--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 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.