All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Switch to PR server model for PR bumps - 1 week
Date: Wed, 05 Dec 2012 15:37:25 +0000	[thread overview]
Message-ID: <1354721845.25268.118.camel@ted> (raw)
In-Reply-To: <20121205152442.GC3396@jama.jama.net>

On Wed, 2012-12-05 at 16:24 +0100, Martin Jansa wrote:
> On Wed, Dec 05, 2012 at 03:19:53PM +0000, Richard Purdie wrote:
> > On Wed, 2012-12-05 at 15:45 +0100, Martin Jansa wrote:
> > Added to the page: "As implemented, values from the PR service are
> > included into the PR field as an addition of the form ".X" so r0 becomes
> > r0.1, r0.2 and so on. This allows existing PR values to be used for
> > whatever reasons allowing manual PR bumps should it be necessary."
> > 
> > (should cover both questions)
> > 
> > As for removing PR, as recipes are upgraded, I'm expecting we will
> > remove PR values so we should get a smooth transition. We can still have
> > PR values, it will just become an exception rather than the rule.
> 
> So default "hidden" r0 is still used in such cases and PRSERV adds again
> just .X.

Exactly.

> Thanks for answers.

They were good questions :)

Cheers,

Richard





  reply	other threads:[~2012-12-05 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 14:13 Switch to PR server model for PR bumps - 1 week Richard Purdie
2012-12-05 14:45 ` Martin Jansa
2012-12-05 15:19   ` Richard Purdie
2012-12-05 15:24     ` Martin Jansa
2012-12-05 15:37       ` Richard Purdie [this message]
2012-12-06  4:20         ` Martin Jansa
2012-12-06 10: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=1354721845.25268.118.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=martin.jansa@gmail.com \
    --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 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.