bitbake.conf: stop exporting PATCH_GET = "0"

Exporting PATCH_GET = "0" has been redundant since patch 2.6.0 was
released in 2009:

  http://git.savannah.gnu.org/cgit/patch.git/commit/?id=b008dece18e6b94b8a13ea44a253855bf407ed01

Host distros which shipped with patch 2.5.x (e.g. Centos 5) are no
longer supported, so this export can be retired from bitbake.conf.

(From OE-Core rev: e9638fe60d24325e85dacc0c1551f671daed5c06)

Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 0 insertions, 10 deletions

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index e80ee18135..1a2f420c74 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -629,16 +629,6 @@ FAKEROOTDIRS = "${PSEUDO_LOCALSTATEDIR}"
 PREFERRED_PROVIDER_virtual/fakeroot-native ?= "pseudo-native"
 
 ##################################################################
-# Miscellaneous utilities.
-##################################################################
-
-# GNU patch tries to be intellgent about checking out read-only files from
-# a RCS, which freaks out those special folks with active Perforce clients
-# the following makes patch ignore RCS:
-
-export PATCH_GET="0"
-
-##################################################################
 # Not sure about the rest of this yet.
 ##################################################################