Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH][jethro] cross-localedef-native: add ABI breaking glibc patch
Date: Mon, 8 Feb 2016 12:18:41 +0200	[thread overview]
Message-ID: <56B86B81.7030000@linux.intel.com> (raw)
In-Reply-To: <CAJTo0Lbm-AM=9tVYnY443RdHYqzs3LUg=tk6mTnaVer54hYpWg@mail.gmail.com>

On 02/05/2016 04:26 PM, Burton, Ross wrote:

> This impacts master too, so I've merged this into ross/mut and endorse
> it for Jethro.
>
> I've also a filed a bug against QA so we notice this breaking on the
> autobuilder...

Yes please; we have all the needed infrastructure to notice these 
regressions via automated testing before they make their way into master.

Alex



  parent reply	other threads:[~2016-02-08 10:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 10:25 [PATCH][jethro] cross-localedef-native: add ABI breaking glibc patch Jens Rehsack
2016-02-05 14:26 ` Burton, Ross
2016-02-05 21:50   ` Andreas Müller
2016-02-06 14:04   ` Jens Rehsack
2016-02-08 10:18   ` Alexander Kanavin [this message]
2016-02-06 15:09 ` Khem Raj

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=56B86B81.7030000@linux.intel.com \
    --to=alexander.kanavin@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox