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: Mon, 31 Oct 2011 10:16:31 +0800	[thread overview]
Message-ID: <4EAE04FF.1070207@windriver.com> (raw)
In-Reply-To: <4EAE0428.2020209@windriver.com>

On 2011年10月31日 10:12, Kang Kai 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 Saul,

And right now is 2 commits behind the latest revision, do it worth to 
update right now?
Thanks!

>
> 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




  reply	other threads:[~2011-10-31  2:21 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 [this message]
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
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=4EAE04FF.1070207@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.