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: Wed, 11 May 2011 10:17:10 +0100 [thread overview]
Message-ID: <1305105430.30391.314.camel@rex> (raw)
In-Reply-To: <20110510202417.GB5171@jama.jama.net>
On Tue, 2011-05-10 at 22:24 +0200, Martin Jansa wrote:
> On Tue, May 10, 2011 at 08:03:57PM +0100, Richard Purdie wrote:
> > Martin/Tom: Serious question - why not use the contrib repo for this?
>
> I have nothing against contrib repo and I'm using oe-core-contrib for
> oe-core stuff, but I had gitorious repos for meta-oe before
> meta-oe-contrib was created and now I didn't feel the need to change it
> and update my modified meta-oe-create-pull-request header :) but I will
> if you or koen find it better to pull from *-contrib (I'm pushing shr
> branch there already anyways).
I have a habit of using the cgit web interface to visualise patches so
using the contrib repo does help me a little. As you say, you're using
oe-core-contrib though so thats fine :)
FWIW, I find the gitorious web interface extremely painful to the point
of being unusable to get the information I want from it. Could just be
me but I have to pull trees somewhere else to look at them I find it
that painful.
Cheers,
Richard
next prev parent reply other threads:[~2011-05-11 9:20 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
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 [this message]
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=1305105430.30391.314.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