xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>,
	Lars Kurth <lars.kurth@citrix.com>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>
Cc: Doug Goldstein <cardoe@cardoe.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xenbits GitHub mirror?
Date: Wed, 27 Jan 2016 16:14:16 +0000	[thread overview]
Message-ID: <1453911256.26591.43.camel@citrix.com> (raw)
In-Reply-To: <56A8E9E8.6050606@citrix.com>

On Wed, 2016-01-27 at 16:01 +0000, George Dunlap wrote:
> On 27/01/16 15:45, Ian Campbell wrote:
> > For most patch series setting up a GH account and pushing the changes to it
> > etc is pure overhead (or at least optional), there is no need to encourage
> > it for most series, nor even necessarily to encourage people to proactively
> > push to a repo, we can always ask if we find the series to hard to review
> > as patches.
> 
> It did take me a while to find a system that made it not a pain to apply
> patch series from xen-devel, and the solution I have now is very
> particular to the combination of e-mail tools that I happen to use; I'm
> not sure how transferrable they are.

I use the script below, which apart from needing a way to see the message
id of mails is independent of any mail tools. For git send-email generated
series I use it as:

    ~/get-msgid -g '2 5' '    <    1447415999-22003-1-git-send-email-olaf@aepfle.de    >    ' | git am

(where 2 and 5 come come from the message id of the first and last patch
mails and it will apply the whole range, note that git send-email often has
patch #1 with msgid=2 due to the cover letter)

> So while I've managed to get things to a point where I don't have much
> pain, it's probably something that could use some work as a project in
> general.  "Encouraging most people to include public git branches" is
> one option to help that; "Having a mail bot that gave you git-am'able
> mbox files" is another.

Sure, but none of that is a blocker for what Doug is actually asking for
feedback on here, which really doesn't need to go off into the weeds
regarding some other future workflow which it may or may not enable, in
order to make a decision.

Ian.

#!/bin/bash

help()
{
    echo "help!" 1>&2
}

GIT=
while getopts g: OPT ; do
        case $OPT in
            g)  GIT="$OPTARG" ;;
            h)  help ; exit 1 ;;
            \?) exit 1 ;;
        esac
done
shift $(expr $OPTIND - 1)

fetch_messages()
{
    for i in $@ ; do
        echo "Fetching Message ID $i" 1>&2
        if [ -n "$X" ] ; then
            ssh celaeno cat /srv/mldrop/xen-devel/"\"$i\""
        else
            #wget -O - -q http://bugs.xenproject.org/xen/mid/"$i"/raw
            i=${i/\+/%2B}
            curl --silent http://bugs.xenproject.org/xen/mid/"$i"/raw
        fi
    done
}

if [ -z "$GIT" ] ; then
    fetch_messages $@
else
    #<1349427871-31195-4-git-send-email-anthony.perard@citrix.com>
    for i in $@ ; do
        PATTERN=$(echo "$i" | sed -e 's/^\(<[0-9]*-[0-9]*-\)[0-9]*\(-.*>\)/\1@@NR@@\2/g')
        echo "GIT pattern $PATTERN" 1>&2
        for n in $(seq $GIT) ; do
            MSG=$(echo "$PATTERN" | sed -e "s/@@NR@@/$n/")
            fetch_messages $MSG
        done
    done
fi

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-01-27 16:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 20:51 xenbits GitHub mirror? Doug Goldstein
2015-12-21 11:54 ` George Dunlap
2015-12-23  8:53   ` Jon Ludlam
2016-01-26 16:48     ` Doug Goldstein
2016-01-26 16:55 ` Ian Campbell
2016-01-26 17:26   ` Doug Goldstein
2016-01-26 22:36     ` Doug Goldstein
2016-01-27  9:34     ` George Dunlap
2016-01-27  9:44       ` Ian Campbell
2016-01-27  9:45     ` Ian Campbell
2016-01-27 10:55       ` Andrew Cooper
2016-01-27 11:21         ` George Dunlap
2016-01-27 15:18           ` Lars Kurth
2016-01-27 15:45             ` Ian Campbell
2016-01-27 16:01               ` George Dunlap
2016-01-27 16:14                 ` Ian Campbell [this message]
2016-02-03 15:38             ` Doug Goldstein

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=1453911256.26591.43.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=george.dunlap@citrix.com \
    --cc=lars.kurth@citrix.com \
    --cc=xen-devel@lists.xen.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).