All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] buildhistory.bbclass: metadata-revs show repo parent
Date: Sat, 12 Mar 2016 17:32:03 -0500	[thread overview]
Message-ID: <56E498E3.8000106@gmail.com> (raw)
In-Reply-To: <CAJTo0Lb23TkQYmVBUpTmOpCgtB-odj9MDZzSrAn4ZzyQKaw6gQ@mail.gmail.com>



On 03/12/16 16:54, Burton, Ross wrote:
>
> On 12 March 2016 at 04:28, Trevor Woerner <twoerner@gmail.com 
> <mailto:twoerner@gmail.com>> wrote:
>
>     openembedded-core/meta =
>     master:00d3fd571a8d261d065b43f5cf3076a381843984
>         meta-openembedded/meta-oe =
>     master:a1e135a499998add7575682bf53db5e02e753580
>         meta-openembedded/meta-gnome =
>     master:a1e135a499998add7575682bf53db5e02e753580
>         meta-rpb          =
>     master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
>         meta-96boards     =
>     master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
>         meta-qcom         =
>     master:32fcda819acb8ec485d9ab05108d554f807bf75d
>         meta-browser      =
>     master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
>         meta-linaro/meta-linaro-toolchain =
>     master:367f784b831938dc508b7d472342d2d0d6ed9769
>         meta-poky/meta    =
>     master:37b61b059031e3c272a929b834e12fd83f46598c
>         meta-poky/meta-poky =
>     master:37b61b059031e3c272a929b834e12fd83f46598c
>
>
> Why are you pulling oe-core/meta and poky/meta into the same build 
> considering they're literally the same layer?  You should either drop 
> oe-core/meta or poky/meta from your bblayers.

Ok, thanks; good point.

>
> However the output showing the full remote URLs seems a sensible 
> improvement to me.
>

My hesitation is whether we want to replace the existing 
buildhistory/metadata-revs with my "improvements" or whether I should 
just create a second file with the updates. I don't want to break 
anyone's process should they have come to rely on that file being as it is.


  reply	other threads:[~2016-03-12 22:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-12  2:49 [PATCH] buildhistory.bbclass: metadata-revs show repo parent Trevor Woerner
2016-03-12  3:59 ` Khem Raj
2016-03-12  4:28   ` Trevor Woerner
2016-03-12  5:33     ` Trevor Woerner
2016-03-12 11:55       ` Khem Raj
2016-03-12 15:26         ` Trevor Woerner
2016-03-12 21:54     ` Burton, Ross
2016-03-12 22:32       ` Trevor Woerner [this message]
2016-03-13 19:25         ` Paul Eggleton
2016-03-13  0:34 ` Trevor Woerner

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=56E498E3.8000106@gmail.com \
    --to=twoerner@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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.