From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 5D064138010 for ; Wed, 3 Apr 2013 16:35:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E9681E0B2C; Wed, 3 Apr 2013 16:35:43 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0EEB9E0B1B for ; Wed, 3 Apr 2013 16:35:42 +0000 (UTC) Received: from pomiocik.lan (77-253-144-190.adsl.inetia.pl [77.253.144.190]) (using SSLv3 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 099C233DD04; Wed, 3 Apr 2013 16:35:40 +0000 (UTC) Date: Wed, 3 Apr 2013 18:36:07 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] How shall we name the EAPI 6 patch applying function? Message-ID: <20130403183607.75fea548@pomiocik.lan> In-Reply-To: <20130403111437.4c1e0aa6@pomiocik.lan> References: <20130403111437.4c1e0aa6@pomiocik.lan> Organization: Gentoo X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.17; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA512; boundary="Sig_/qivcAJPVFDGcRIV5JNZmOpS"; protocol="application/pgp-signature" X-Archives-Salt: 6a61b1d8-98e2-4d25-b6cf-ee630dbd2d5e X-Archives-Hash: 1da40bb0fe121f42b8a4e6e32ab9113f --Sig_/qivcAJPVFDGcRIV5JNZmOpS Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, 3 Apr 2013 11:14:37 +0200 Micha=C5=82 G=C3=B3rny wrote: > Therefore, I ask you: how should we name the new (and simpler) patch > applying function which will be provided in EAPI 6? My propositions: - apply_patches ... - apply_user_patches Where I think we used the latter name when discussing adding user patch support. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/qivcAJPVFDGcRIV5JNZmOpS Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQJ8BAEBCgBmBQJRXFp8XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1RUJGMjBGOTk2RkIzQzIyQ0M2RkNBNDBC QUJGMUQ1RkY4QzgxMTBBAAoJELq/HV/4yBEKWtkP/2OEw8eZSIcKx++6cqJ5SaGe wxoTTLPDxIE12OaofdVujkxT++ZO4hp8GeC4B4T2KbmgQ91/jgV9N/wZk5tsjZPS zzogy0swxyZk5uO8RUt6ChF/usu7Ai3mtJluO4Klf8hrE+MnRGDNuNsUFZIWXai0 Dl8eiTKbN+Efkn4S3WSvJjL16H7vWKCIBeDW4zefikl7wB4sOdEZwFcLy4WldNo/ CVX9s1joBI0quZODVsyf00tXDZNjbqHl6v4XsHTpyeiYqocIdSWBU1dqsZOcM+yf 7KT2jX4iHDklgwrwvmKNLlPKcaMsEy49/mTixKdLJnnLzy87x8qJeMj1xbQubt2h qWtf8rRVgTRUW3sRxPXNsINIhzKqgwHQx+1OPcDWykwHBPYJFEvHb/uE95LMJvGh /ylhAe+43/8kPrNBT4uslun9UH5AKXR4UryI1pxYdWy9cOOPJ4wqJ83RENwPNqrH 8Lj9b1OlomCxBh+2gcAjr8RTzH7bZMY3dvClAEWgRWOsOSEBaYILr6nAfkv6eoh/ A6eQI6mREQEJvvprXbujOgKMWyapYFEMuvgYch2Mf9mBQVKAFZhLvOvvMZQaQqIo oytxkGHU/vh5mv7jLBuwzVzBLuvEJLVMtPCPBOgmQssROVLdpub06tY8EEyxzYD6 ui1Ha8MrUbHgaAH5IJpC =cXQ9 -----END PGP SIGNATURE----- --Sig_/qivcAJPVFDGcRIV5JNZmOpS--