All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Saul Wold <saul.wold@intel.com>
Subject: Re: What is the strategy to update eglibc?
Date: Thu, 17 Nov 2011 10:32:55 +0800	[thread overview]
Message-ID: <4EC47257.5030302@windriver.com> (raw)
In-Reply-To: <CAMKF1spV_BiCTo1YCoKL7XUTqRWtFJFYP4yB16FoyETjYzAuxg@mail.gmail.com>

On 2011年11月17日 05:38, Khem Raj wrote:
> On Sun, Oct 30, 2011 at 7:12 PM, Kang Kai<Kai.Kang@windriver.com>  wrote:
>> Hi Saul,
>>
>> I just want to update eglibc but eglibc is using its 2.14 branch and use svn
>> commit revision "15225" as current version. Of course it is behind the
>> latest svn revision, but I don't quit sure about which is the right revision
>> to update eglibc.

Hi Khem,
> since release branches of eglibc only get bug fixes in ideal case it
> should be good at any revision. However if we have bug
> fixes that dont affect us immediately we do not tend to update
> the revision. If you find that some bug fix thats applied upstream is
> needed it certainly can be a reason to bump up srcrev given we do some
> level of build and runtime testing
> with new revision.

Thanks very much for your detailed explanation.
I check the changelog of eglibc 2.13 branch(latest is 15508), and they 
are some tiny updates except the revision 15226 that is same with 
current patch

glibc_bug_fix_12454.patch

And I made the rough tests of image-sato of qemu-x86 and qemu-arm and 
results are fine.

Regards,
Kai
>
>> Could you give me some guide? Thank you!
>>
>> Regards,
>> Kai
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2011-11-17  2:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31  2:12 What is the strategy to update eglibc? Kang Kai
2011-10-31  2:16 ` Kang Kai
2011-10-31 16:43   ` Saul Wold
2011-11-01  2:07     ` Kang Kai
2011-11-16 21:38 ` Khem Raj
2011-11-17  2:32   ` Kang Kai [this message]
2011-11-17  2:35     ` Ni Qingliang
2011-11-17  6:41       ` Khem Raj
2011-11-17  6:56         ` Ni Qingliang
2011-11-17  8:09       ` McClintock Matthew-B29882

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=4EC47257.5030302@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=saul.wold@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.