ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] services needed from kernel.org infrastructure
Date: Wed, 8 Jul 2015 10:01:32 +0200	[thread overview]
Message-ID: <CAMuHMdU0sYYNmViTRw3ZtmBzwUxrTen50VunpEJwYahVYO2d9g@mail.gmail.com> (raw)
In-Reply-To: <CALCETrWywXiKcWc4jSQR1n9nuwVom81w0qnBo7_HRV7qNahURQ@mail.gmail.com>

On Wed, Jul 8, 2015 at 1:31 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> On Tue, Jul 7, 2015 at 1:42 PM, Jiri Kosina <jkosina@suse.com> wrote:
>> I think it'd be useful to have a session where maintainers could come up
>> with feature / improvement requests for kernel.org infrastructure and have
>> a subsequent discussion about whether they would be generally useful.
>>
>> Let me start with my personal wish:
>>
>> I personally would very welcome a facility that'd send out an e-mail if a
>> new commit is pushed to a git.kernel.org repo branch (sort of what tip-bot
>> and akpm's scripts are doing these days) to automatically notify the patch
>> author that the patch has been merged and pushed out.
>>
>> Suggested attendance: Konstantin, maintainers :)
>
> I wouldn't mind something like patchwork for lkml.  Since I use gmail
> (sigh), it's a minor PITA to pull out patchbombs in git am-able
> format.

For backup purposes, I run getmail from cron to download all my gmail
email.

To pull out a patchbomb:
  1. Select "Show original" in gmail for the cover letter,
  2. Copy Message-Id,
  3. Run "gmail-extract-patch-series message-id /tmp/cool-patch-series-"
     from the directory that contains the downloaded emails (I use one
     directory per day),
  4. git am -s /tmp/cool-patch-series-*.patch

$ cat $(type -p gmail-extract-patch-series)
#!/bin/bash

set -e

function usage()
{
        cat <<END

Usage: $(basename $0) <message-id> <prefix> [ <files> ... ]

END
        exit -1
}


if [ $# -lt 2 ]; then
        usage
fi

mid=$1
prefix=$2
shift
shift

if [ $# -lt 1 ]; then
        files=*
else
        files=$*
fi

for src in $(grep -l $mid $files); do
        if grep -m 1 "^Subject: Re: " $src > /dev/null; then
                echo Ignoring reply in $src
        else
                i=$(grep ^Subject: $src | sed -e 's@/.*$@@g' -e 's@^.* @@g')
                case $i in
                0|00|000) # Sending more than 999 patches is insane
                       suffix=txt
                        ;;
                *)
                        suffix=patch
                        ;;
                esac
                dst=$prefix$i.$suffix
                echo Extracting \"$(grep ^Subject $src | sed -e
's@Subject: @@g')\" to $dst
                cp -i $src $dst
        fi
done
$

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  parent reply	other threads:[~2015-07-08  8:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 20:42 Jiri Kosina
2015-07-07 22:40 ` Mark Brown
2015-07-07 22:52   ` Dmitry Torokhov
2015-07-08  2:16     ` Greg KH
2015-07-08  8:02       ` Jiri Kosina
2015-07-08  9:35         ` Mark Brown
2015-07-08 14:01           ` Theodore Ts'o
2015-07-08 14:36             ` Jason Cooper
2015-07-08 14:40             ` Jiri Kosina
2015-07-08 15:00             ` Greg KH
2015-07-12 12:55             ` Fengguang Wu
2015-07-13 16:22               ` Steven Rostedt
2015-07-14 13:07                 ` Fengguang Wu
2015-07-08 14:59         ` Greg KH
2015-07-08 15:08           ` Jiri Kosina
2015-07-08 15:42             ` Steven Rostedt
2015-07-07 22:53   ` josh
2015-07-08  7:35   ` Jiri Kosina
2015-07-08 13:05   ` Jason Cooper
2015-07-07 23:31 ` Andy Lutomirski
2015-07-07 23:37   ` Guenter Roeck
2015-07-07 23:38     ` Andy Lutomirski
2015-07-08  8:01   ` Geert Uytterhoeven [this message]
2015-07-08  7:31 ` James Bottomley
2015-07-08 13:25 ` Konstantin Ryabitsev

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=CAMuHMdU0sYYNmViTRw3ZtmBzwUxrTen50VunpEJwYahVYO2d9g@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=luto@amacapital.net \
    /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