Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	openembedded-devel@lists.openembedded.org,
	openembedded-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] [RFC] Layers, PRINC and bbappends
Date: Thu, 16 May 2013 11:29:05 +0200	[thread overview]
Message-ID: <20130516092905.GG24809@jama.dyndns-home.com> (raw)
In-Reply-To: <24887939.8KrA2KDk4J@helios>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

On Thu, May 16, 2013 at 10:10:45AM +0100, Paul Eggleton wrote:
> On Thursday 16 May 2013 10:59:54 Martin Jansa wrote:
> > On Thu, May 16, 2013 at 09:29:48AM +0100, Paul Eggleton wrote:
> > > On Thursday 16 May 2013 08:31:33 Koen Kooi wrote:
> > > > Removing layers is pretty much impossible, though.
> > > 
> > > With PRINC gone would there be any other issue that would make removing
> > > layers a problem?
> > 
> > Does PR service really fix removing layers? I don't think so, if you add
> > layer and checksum of foo is changed AUTOPR is incremented, but then you
> > remove the layer and the checksum is unfortunately the same as what you
> > had before AUTOPR will go backwards.
> 
> Then I would have to say if that's not the behaviour you want we should change 
> it or at least make it optional to force it to always increment even if the 
> checksum is the same as a previous value.

That won't work with multiple builders using the same PR server (I don't
wont other builders to always increment PRAUTOs used in builds which
populate official feed).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-05-16  9:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <40EC58CA-E878-4F77-8E39-4F8D86F48E29@dominion.thruhere.net>
2013-05-15 20:33 ` [oe] [RFC] Layers, PRINC and bbappends Richard Purdie
2013-05-15 23:02   ` Paul Barker
2013-05-22  8:47     ` Paul Barker
2013-05-22  9:17       ` Martin Jansa
2013-05-22 10:08         ` Paul Eggleton
2013-05-22 10:14       ` Phil Blundell
2013-05-23  2:50         ` Chris Larson
2013-05-27 12:07           ` Paul Barker
2013-05-16  6:23   ` Koen Kooi
2013-05-16  8:37     ` Paul Eggleton
2013-05-16  9:27       ` Martin Jansa
     [not found] ` <1499979.6pTC18VfFV@helios>
2013-05-16  6:31   ` Koen Kooi
2013-05-16  8:29     ` Paul Eggleton
2013-05-16  8:59       ` Martin Jansa
2013-05-16  9:10         ` Paul Eggleton
2013-05-16  9:29           ` Martin Jansa [this message]
2013-05-16 20:15             ` Richard Purdie

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=20130516092905.GG24809@jama.dyndns-home.com \
    --to=martin.jansa@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox