From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Cc: Denis OSTERLAND <denis.osterland@diehl.com>
Subject: Re: [ptxdist] [PATCH] sudo: version bump 1.8.9p5 -> 1.8.21p2
Date: Fri, 15 Sep 2017 13:44:53 +0200 [thread overview]
Message-ID: <4744907.xCR3fbpn4R@ada> (raw)
In-Reply-To: <1505462546-11397-1-git-send-email-Denis.Osterland@diehl.com>
Hello Denis,
Am Freitag, 15. September 2017, 08:07:15 CEST schrieb Denis OSTERLAND:
> Signed-off-by: Denis Osterland <Denis.Osterland@diehl.com>
> ---
> .../0001-install-sh-disable-stripping.patch | 25
> ++++++++++++++++++++++ patches/sudo-1.8.21p2/series |
> 4 ++++
> .../0001-install-sh-disable-stripping.patch | 25
> ---------------------- patches/sudo-1.8.9p5/series |
> 4 ----
> rules/sudo.make | 5 +++--
> 5 files changed, 32 insertions(+), 31 deletions(-)
> create mode 100644
> patches/sudo-1.8.21p2/0001-install-sh-disable-stripping.patch create mode
> 100644 patches/sudo-1.8.21p2/series
> delete mode 100644
> patches/sudo-1.8.9p5/0001-install-sh-disable-stripping.patch delete mode
> 100644 patches/sudo-1.8.9p5/series
Could you please pass -M or --find-renames to `git format-patch` next time?
This would make reviewing things easier if some files were renamed only. Those
diffs to and from null would not distract anymore. The above quoted part would
look like this then:
---
.../0001-install-sh-disable-stripping.patch | 0
patches/{sudo-1.8.9p5 => sudo-1.8.21p2}/series | 0
rules/sudo.make | 5 ++
+--
3 files changed, 3 insertions(+), 2 deletions(-)
rename patches/{sudo-1.8.9p5 => sudo-1.8.21p2}/0001-install-sh-disable-
stripping.patch (100%)
rename patches/{sudo-1.8.9p5 => sudo-1.8.21p2}/series (100%)
Greets
Alex
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-09-15 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 8:07 Denis OSTERLAND
2017-09-15 11:44 ` Alexander Dahl [this message]
2017-09-15 12:13 ` Denis OSTERLAND
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=4744907.xCR3fbpn4R@ada \
--to=ada@thorsis.com \
--cc=denis.osterland@diehl.com \
--cc=ptxdist@pengutronix.de \
/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