Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] stop exporting PATCH_GET = "0"
Date: Wed, 27 Jan 2016 18:11:08 -0800	[thread overview]
Message-ID: <1453947071-13364-1-git-send-email-armccurdy@gmail.com> (raw)

Andre McCurdy (3):
  bitbake.conf: stop exporting PATCH_GET = "0"
  gcc-cross.inc: drop pruning of PATCH_GET from the testgcc script
  glibc-testing.inc: drop pruning of PATCH_GET from the testglibc script

 meta/conf/bitbake.conf                    | 10 ----------
 meta/recipes-core/glibc/glibc-testing.inc |  1 -
 meta/recipes-devtools/gcc/gcc-cross.inc   |  1 -
 3 files changed, 12 deletions(-)

-- 
1.9.1



             reply	other threads:[~2016-01-28  2:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28  2:11 Andre McCurdy [this message]
2016-01-28  2:11 ` [PATCH 1/3] bitbake.conf: stop exporting PATCH_GET = "0" Andre McCurdy
2016-01-28  2:11 ` [PATCH 2/3] gcc-cross.inc: drop pruning of PATCH_GET from the testgcc script Andre McCurdy
2016-01-28  2:11 ` [PATCH 3/3] glibc-testing.inc: drop pruning of PATCH_GET from the testglibc script Andre McCurdy

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=1453947071-13364-1-git-send-email-armccurdy@gmail.com \
    --to=armccurdy@gmail.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