From: Saul Wold <saul.wold@intel.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: dpatch files in Yocto tree
Date: Thu, 12 May 2011 17:20:52 -0700 [thread overview]
Message-ID: <4DCC7964.6010208@intel.com> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94D8968844@orsmsx504.amr.corp.intel.com>
On 05/12/2011 09:49 AM, Kamble, Nitin A wrote:
> I find following dpatch files in the Yocto tree. Dpatch files have a
> small shell script at the beginning of the patch.
>
> Out of all these, all gcc patches are for all gcc-4.3.3 only, which is
> kind of outdated stuff now. And will be going out of the tree soon.
>
> Binutils & tslib patches are in current use. Adding metadata vars likes
> upstream_status may break the dpatch format/script.
>
> Do we care for the shell script inside the dpatch file? Is it ok to
> break it inside Yocto tree?
>
I think you can add the Upstream-Status: after the exit on the script
and before the patch proper starts.
Have you confirmed that all these patches are actually used? I think
that some are no longer used.
Also as Richard suggested, please put an RFC Patch that remove the
oldest version of GCC 4.3.3, along with gcc-cross-kernel-3.4.4 as it's
no longer needed either.
> meta/recipes-devtools/binutils/binutils-2.21/binutils-uclibc-300-012_check_ldrunpath_length.patch
>
> meta/recipes-devtools/binutils/binutils-2.21/binutils-uclibc-300-001_ld_makefile_patch.patch
>
> meta/recipes-devtools/binutils/binutils-2.21/binutils-x86_64_i386_biarch.patch
>
> meta/recipes-devtools/binutils/binutils-2.21/binutils-uclibc-300-006_better_file_error.patch
>
> meta/recipes-devtools/gcc/gcc-4.5.1/libstdc++-pic.dpatch
>
> meta/recipes-devtools/gcc/gcc-4.5.1/arm-unbreak-eabi-armv4t.dpatch
>
> meta/recipes-devtools/gcc/gcc-4.5.1/gcc-ice-hack.dpatch
>
> meta/recipes-devtools/gcc/gcc-4.5.1/pr30961.dpatch
>
> meta/recipes-devtools/gcc/gcc-4.6.0/libstdc++-pic.dpatch
>
> meta/recipes-devtools/gcc/gcc-4.6.0/arm-unbreak-eabi-armv4t.dpatch
>
> meta/recipes-devtools/gcc/gcc-4.6.0/gcc-ice-hack.dpatch
>
> meta/recipes-devtools/gcc/gcc-4.6.0/pr30961.dpatch
>
> meta/recipes-devtools/gcc/gcc-4.3.3/300-libstdc++-pic.patch
>
> meta/recipes-devtools/gcc/gcc-4.3.3/debian/libstdc++-pic.dpatch
>
> meta/recipes-devtools/gcc/gcc-4.3.3/debian/arm-unbreak-eabi-armv4t.dpatch
>
> meta/recipes-devtools/gcc/gcc-4.3.3/debian/gcc-ice-hack.dpatch
>
> meta/recipes-devtools/gcc/gcc-4.3.3/debian/pr30961.dpatch
>
> meta/recipes-graphics/tslib/tslib/32bitBE-support.patch
>
> Thanks,
>
> Nitin
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
prev parent reply other threads:[~2011-05-13 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 16:49 dpatch files in Yocto tree Kamble, Nitin A
2011-05-13 0:20 ` Saul Wold [this message]
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=4DCC7964.6010208@intel.com \
--to=saul.wold@intel.com \
--cc=nitin.a.kamble@intel.com \
--cc=yocto@yoctoproject.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.