All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/5] perf: drop PR
Date: Tue, 17 Mar 2015 15:48:02 +0200	[thread overview]
Message-ID: <CAJTo0LYcmMzAd-q84HhmCO38XJjWmdnGPQAe+X-EqieBoUER-Q@mail.gmail.com> (raw)
In-Reply-To: <55081BFD.40607@windriver.com>

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

On 17 March 2015 at 14:20, Bruce Ashfield <bruce.ashfield@windriver.com>
wrote:

> But doesn't that mean that my bash RDEPENDS fix needs a PR
> bump ?
>

No, you don't need to bump as the PR service will bump when it rebuilds.

Ross

[-- Attachment #2: Type: text/html, Size: 666 bytes --]

  reply	other threads:[~2015-03-17 13:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 17:27 [PATCH 0/5] kernel: consolidated pull request Bruce Ashfield
2015-03-16 17:27 ` [PATCH 1/5] kern-tools: fix iterative configuration runs Bruce Ashfield
2015-03-16 17:27 ` [PATCH 2/5] kernel-yocto: split meta data generation from patching phase Bruce Ashfield
2015-03-17  6:52   ` Burton, Ross
2015-03-17 12:21     ` Bruce Ashfield
2015-03-17 13:49       ` Burton, Ross
2015-03-17 13:50         ` Bruce Ashfield
2015-03-17 13:51           ` Burton, Ross
2015-03-16 17:27 ` [PATCH 3/5] linux-yocto/3.19: integrate korg -stable update Bruce Ashfield
2015-03-16 17:27 ` [PATCH 4/5] perf: drop PR Bruce Ashfield
2015-03-17  7:01   ` Burton, Ross
2015-03-17 12:20     ` Bruce Ashfield
2015-03-17 13:48       ` Burton, Ross [this message]
2015-03-17 13:50         ` Bruce Ashfield
2015-03-17 13:52           ` Burton, Ross
2015-03-16 17:27 ` [PATCH 5/5] perf: add bash to RDEPENDS Bruce Ashfield

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=CAJTo0LYcmMzAd-q84HhmCO38XJjWmdnGPQAe+X-EqieBoUER-Q@mail.gmail.com \
    --to=ross.burton@intel.com \
    --cc=bruce.ashfield@windriver.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.