All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Dpkg: Fix broken patch
Date: Sat, 18 Apr 2015 08:58:48 +0100	[thread overview]
Message-ID: <1429343928.6976.208.camel@linuxfoundation.org> (raw)
In-Reply-To: <1429326365-25767-1-git-send-email-sgw@linux.intel.com>

On Fri, 2015-04-17 at 20:06 -0700, Saul Wold wrote:
> Richard,
> 
> Major mia culpa! 
> 
> I tested sgw/dizzy and then manged to push another patch from a different branch, I had this
> patch queued up and it ran on the AB before I pushed the wrong branch.
> 
> Please pull this patch (it's the correct one), and reset the Build Appliance SRCREV, I 
> will try to start an RC2 build this weekend.

Ok, merged. Fired a master-next in the meantime.

Cheers,

Richard



      parent reply	other threads:[~2015-04-18  7:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-18  3:06 [PATCH] Dpkg: Fix broken patch Saul Wold
2015-04-18  3:06 ` [PATCH] dpkg: Fix patch to adjust for older code Saul Wold
2015-04-18  7:58 ` Richard Purdie [this message]

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=1429343928.6976.208.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@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 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.