Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Pull request with misc changes
Date: Tue, 10 May 2011 20:03:57 +0100	[thread overview]
Message-ID: <1305054238.30391.283.camel@rex> (raw)
In-Reply-To: <4DC98507.6070103@mentor.com>

On Tue, 2011-05-10 at 11:33 -0700, Tom Rini wrote:
> On 05/10/2011 11:13 AM, Martin Jansa wrote:
> > I'm using slightly modified script for pull requests from gitorious.
> > 
> > send-pull-request are the same as long as you use git send-email and
> > have sendemail.to defined in repo.
> > 
> > To modify it for github is as simple as this I guess.
> > 
> > $ diff -uNr shr-core/openembedded-core/scripts/create-pull-request ~/bin/meta-efl-create-pull-request 
> > --- shr-core/openembedded-core/scripts/create-pull-request 2011-04-04 09:35:47.973626385 +0200
> > +++ /OE/bin/meta-efl-create-pull-request        2011-05-10 13:33:20.349688815 +0200
> > @@ -2,9 +2,11 @@
> >  ODIR=pull-$$
> >  RELATIVE_TO="master"
> >  COMMIT_ID="HEAD"
> > -PULL_URL="git://git.openembedded.org/openembedded-core-contrib"
> > -WEB_URL_PREFIX="http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h="
> > -PREFIX="PATCH"
> > +#PULL_URL="git://git.openembedded.org/meta-openembedded-contrib"
> > +#WEB_URL_PREFIX="http://git.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h="
> > +PULL_URL="git://gitorious.org/shr/meta-openembedded.git"
> > +WEB_URL_PREFIX="http://gitorious.org/shr/meta-openembedded/commits/"
> > +PREFIX="meta-efl][PATCH"
> >  
> >  usage() {
> >  CMD=$(basename $0)
> 
> Hmmm.  I'm going to take a stab at making this a create-pull-request
> option...

Martin/Tom: Serious question - why not use the contrib repo for this?

I have nightmares about all the development being spread to all the
corners of the globe and people not being able to see what is being
worked on. For short lived branches its not so much of a problem but as
we take on longer lived feature development it will be a problem. I'd
therefore like to understand why the dislike of it...

Cheers,

Richard




  reply	other threads:[~2011-05-10 19:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 19:15 Pull request with misc changes Otavio Salvador
2011-05-10  5:17 ` Saul Wold
2011-05-10 12:53   ` Otavio Salvador
2011-05-10 18:00     ` Saul Wold
2011-05-10 18:13       ` Martin Jansa
2011-05-10 18:33         ` Tom Rini
2011-05-10 19:03           ` Richard Purdie [this message]
2011-05-10 19:15             ` Otavio Salvador
2011-05-10 19:32               ` Richard Purdie
2011-05-10 19:36               ` Chris Larson
2011-05-10 20:24             ` Martin Jansa
2011-05-10 21:31               ` Koen Kooi
2011-05-11  9:17               ` Richard Purdie
2011-05-11 10:06                 ` Koen Kooi
2011-05-10 18:20       ` Otavio Salvador
2011-05-11  5:39         ` Darren Hart

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=1305054238.30391.283.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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