From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Marko Lindqvist <cazfi74@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 04/15] file: replace obsolete automake macros with working ones
Date: Mon, 07 Jan 2013 11:59:01 +0000 [thread overview]
Message-ID: <1357559941.25855.7.camel@ted> (raw)
In-Reply-To: <1357516181-5358-5-git-send-email-cazfi74@gmail.com>
On Mon, 2013-01-07 at 01:49 +0200, Marko Lindqvist wrote:
> Add obsolete-automake-macros.patch that replaces automake macros
> no longer supported by automake-1.13 with modern constructs.
>
> Signed-off-by: Marko Lindqvist <cazfi74@gmail.com>
> ---
> .../file/file/obsolete_automake_macros.patch | 15 +++++++++++++++
> meta/recipes-devtools/file/file_5.11.bb | 3 ++-
> 2 files changed, 17 insertions(+), 1 deletion(-)
> create mode 100644 meta/recipes-devtools/file/file/obsolete_automake_macros.patch
>
> diff --git a/meta/recipes-devtools/file/file/obsolete_automake_macros.patch b/meta/recipes-devtools/file/file/obsolete_automake_macros.patch
> new file mode 100644
> index 0000000..8b0d34c
> --- /dev/null
> +++ b/meta/recipes-devtools/file/file/obsolete_automake_macros.patch
> @@ -0,0 +1,15 @@
> +Upstream-Status: Fixed in file-5.12
Can we use a standard syntax for this, something like:
Upstream-Status: Backport (fixed in file-5.12)
(as mentioned in
https://wiki.yoctoproject.org/wiki/Contribution_Guidelines#Patch_Header_Recommendations)
for the same reasons as I just mentioned to Marcin - so we can tell from
scripts what status patches have and it helps reviewers in future know
this can be dropped. The aim is to push patches upstream and standard
syntax means we can get real numbers for how many patches we're
carrying.
I appreciate you can read and tell from the above what it means but I
really want to try and use a consistent syntax.
Cheers,
Richard
next prev parent reply other threads:[~2013-01-07 12:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 23:49 Prepare recipes for automake-1.13 (batch 1 / v2) Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 01/15] pkg-config: replace obsolete automake macros with working ones Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 02/15] libtool: remove help2man dependency Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 03/15] bison: " Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 04/15] file: replace obsolete automake macros with working ones Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 05/15] popt: disable tests Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 06/15] glib-2.0: replace obsolete automake macros with working ones Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 07/15] libx11: disable tests Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 08/15] libpng: replace obsolete automake macros with working ones Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 09/15] libusb: " Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 10/15] pixman: " Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 11/15] libid3tag: " Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 12/15] libgcrypt: " Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 13/15] gnutls: " Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 14/15] libtasn1: remove help2man dependency Marko Lindqvist
2013-01-06 23:49 ` [PATCH v2 15/15] flac: replace obsolete automake macros with working ones Marko Lindqvist
2013-01-07 11:59 ` Richard Purdie [this message]
2013-01-07 12:11 ` [PATCH v2 04/15] file: " Marko Lindqvist
2013-01-07 12:16 ` Burton, Ross
2013-01-07 12:18 ` Otavio Salvador
2013-01-07 13:46 ` Richard Purdie
2013-01-07 15:58 ` Otavio Salvador
2013-01-07 16:26 ` Marko Lindqvist
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=1357559941.25855.7.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=cazfi74@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