From: Phil Blundell <pb@pbcl.net>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] xterm: revert FILES_PN change from recent package uprev
Date: Sun, 31 Jan 2016 22:39:31 +0000 [thread overview]
Message-ID: <1454279971.7421.31.camel@pbcl.net> (raw)
In-Reply-To: <20160131215146.GB8889@windriver.com>
On Sun, 2016-01-31 at 16:51 -0500, Paul Gortmaker wrote:
> If i go into poky/meta-openembedded, and crack open .git/config I'll see
> the source git://git.openembedded.org/meta-openembedded listed. So I
> think at least at that point, I need to look at OE lists and not yocto
> lists. But looking the 2nd link above I'm still none the wiser where in
> OE the xterm patch needs to be sent to, and OE-core looks right until I
> clone core and find the file simply isn't there.
I agree that this is confusing, and the way that poky merges all the
layers together into a single tree doesn't help. But in fact I think
you were already 90% of the way there. Once you've figured out that
this is part of meta-openembedded, you just need to consult the README
file in the appropriate subdir, for example:
http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/README
(which, I assume, also shows up in your poky checkout although I haven't
checked this)
> Is there a 1:1 mapping between mailing lists <---> git://<server>/<path>
> out there, since I think that would help. And/or maybe a get_maintainer
> script like the kernel has.
Not that I know of, but that sounds like a good idea. Perhaps it could
be added to the layer index page:
http://layers.openembedded.org/layerindex/branch/master/layers/
p.
next prev parent reply other threads:[~2016-01-31 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 19:56 [PATCH] xterm: revert FILES_PN change from recent package uprev Paul Gortmaker
2016-01-31 20:45 ` Phil Blundell
2016-01-31 21:51 ` Paul Gortmaker
2016-01-31 22:39 ` Phil Blundell [this message]
2016-01-31 23:05 ` Burton, Ross
2016-01-31 23:23 ` Paul Gortmaker
2016-01-31 23:07 ` Burton, Ross
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=1454279971.7421.31.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.gortmaker@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox