All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brendan Le Foll <brendan.le.foll@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: uclibc recipes in oe-core versioning & using upstream
Date: Fri, 14 Nov 2014 16:21:32 +0000	[thread overview]
Message-ID: <20141114162131.GG15651@jupiter.iwi.intel.com> (raw)

I'm trying to understand the logic behind the uclibc recipes, it seems
it is using fairly random points in history of git master and not the
0.9.33 point releases that have been made.

What is the logic behind that and why not use the upstream release
builds as a starting point?

Thanks,
Brendan


             reply	other threads:[~2014-11-14 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14 16:21 Brendan Le Foll [this message]
2014-11-15  3:02 ` uclibc recipes in oe-core versioning & using upstream 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=20141114162131.GG15651@jupiter.iwi.intel.com \
    --to=brendan.le.foll@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 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.