From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] support/scripts/apply-patches.sh: do not apply patches with renames
Date: Sun, 25 Jun 2017 10:42:37 +0200 [thread overview]
Message-ID: <20170625084237.GA3673@scaer> (raw)
In-Reply-To: <20170624195936.31528-1-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2017-06-24 21:59 +0200, Thomas Petazzoni spake thusly:
> Patches with renames apply properly with patch >= 2.7, but not with
> older patch versions. Since "git format-patch" by default generates
> patches with renames, Buildroot developers often don't realize that
> their patches will not apply properly on build machines that have
> patch < 2.7. In order to prevent such a situation from happening
> again, this commit adds some logic in apply-patches.sh to refuse
> applying patches that contain renames.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
A small nit below...
> ---
> Changes since v1:
> - Use "&&" for the "grep -q && grep -q" condition, as noticed by Yann
> E. Morin.
> ---
> support/scripts/apply-patches.sh | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/support/scripts/apply-patches.sh b/support/scripts/apply-patches.sh
> index 7ccb39d..0c24175 100755
> --- a/support/scripts/apply-patches.sh
> +++ b/support/scripts/apply-patches.sh
> @@ -113,6 +113,11 @@ function apply_patch {
> echo " to be applied : ${path}/${patch}"
> exit 1
> fi
> + if grep -q "^rename from" ${path}/${patch} && \
> + grep -q "^rename to" ${path}/${patch} ; then
> + echo "Error: patch contains some renames, not supported by old patch versions"
> + exit 1
This file a space-leading, but here you have a tab...
Otherwise:
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
> + fi
> echo "${path}/${patch}" >> ${builddir}/.applied_patches_list
> ${uncomp} "${path}/$patch" | patch -g0 -p1 -E -d "${builddir}" -t -N $silent
> if [ $? != 0 ] ; then
> --
> 2.9.4
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-06-25 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 19:59 [Buildroot] [PATCH v2] support/scripts/apply-patches.sh: do not apply patches with renames Thomas Petazzoni
2017-06-24 22:08 ` Arnout Vandecappelle
2017-06-25 8:42 ` Yann E. MORIN [this message]
2017-09-19 21:01 ` Arnout Vandecappelle
2017-09-19 21:07 ` Yann E. MORIN
2017-09-20 17:14 ` Peter Korsgaard
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=20170625084237.GA3673@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.