From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches, Darren Hart <dvhart@linux.intel.com>,
oe-core layer <openembedded-core@lists.openembedded.org>,
Otavio, "poky@yoctoproject.org" <poky@yoctoproject.org>,
Martin Jansa <martin.jansa@gmail.com>
Subject: Re: RFC: create-pull-request / send-pull-request updates
Date: Wed, 11 May 2011 18:40:37 +0100 [thread overview]
Message-ID: <1305135637.30391.455.camel@rex> (raw)
In-Reply-To: <BANLkTintvgFGKUUUdvq2M7Q=m+gYuzs2-A@mail.gmail.com>
On Wed, 2011-05-11 at 10:01 -0700, Khem Raj wrote:
> On Wed, May 11, 2011 at 9:15 AM, Darren Hart <dvhart@linux.intel.com> wrote:
> >
> > Thoughts/Comments?
> >
>
> I would suggest to alter the process a bit and get rid of the scripts
> completely. Patches are sent to mailing list for review once reviewed
> the final patches are
> sent as git pull-request. It would simplify things.
I'd argue that it doesn't. It just means the requests come in different
formats, sometimes with key pieces of information missing which means
the people trying to handle the requests (like me) get frustrated.
I find it easiest to deal with requests that have come through those
scripts.
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
Darren Hart <dvhart@linux.intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
"poky@yoctoproject.org" <poky@yoctoproject.org>,
Tom Rini <tom_rini@mentor.com>
Subject: Re: RFC: create-pull-request / send-pull-request updates
Date: Wed, 11 May 2011 18:40:37 +0100 [thread overview]
Message-ID: <1305135637.30391.455.camel@rex> (raw)
In-Reply-To: <BANLkTintvgFGKUUUdvq2M7Q=m+gYuzs2-A@mail.gmail.com>
On Wed, 2011-05-11 at 10:01 -0700, Khem Raj wrote:
> On Wed, May 11, 2011 at 9:15 AM, Darren Hart <dvhart@linux.intel.com> wrote:
> >
> > Thoughts/Comments?
> >
>
> I would suggest to alter the process a bit and get rid of the scripts
> completely. Patches are sent to mailing list for review once reviewed
> the final patches are
> sent as git pull-request. It would simplify things.
I'd argue that it doesn't. It just means the requests come in different
formats, sometimes with key pieces of information missing which means
the people trying to handle the requests (like me) get frustrated.
I find it easiest to deal with requests that have come through those
scripts.
Cheers,
Richard
next prev parent reply other threads:[~2011-05-11 17:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 16:15 RFC: create-pull-request / send-pull-request updates Darren Hart
2011-05-11 16:15 ` Darren Hart
2011-05-11 16:22 ` [poky] " Koen Kooi
2011-05-11 16:22 ` Koen Kooi
2011-05-11 18:06 ` [poky] " Darren Hart
2011-05-11 18:06 ` Darren Hart
2011-05-11 17:01 ` Khem Raj
2011-05-11 17:01 ` Khem Raj
2011-05-11 17:40 ` Richard Purdie [this message]
2011-05-11 17:40 ` Richard Purdie
2011-05-11 18:24 ` Darren Hart
2011-05-11 18:24 ` Darren Hart
2011-05-12 2:43 ` Khem Raj
2011-05-12 2:43 ` Khem Raj
2011-05-11 18:35 ` Tom Rini
2011-05-11 18:35 ` Tom Rini
2011-05-12 0:49 ` Otavio Salvador
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=1305135637.30391.455.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
--cc=raj.khem@gmail.com \
/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.