From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC v2 PATCH] get_maintainer: fix perl 5.22/5.24 deprecated/incompatible "\C" use
Date: Thu, 07 Jan 2016 17:13:59 +0100 [thread overview]
Message-ID: <20160107161359.5ED03380311@gemini.denx.de> (raw)
In-Reply-To: <1452170739-31351-1-git-send-email-hs@denx.de>
Dear Heiko,
In message <1452170739-31351-1-git-send-email-hs@denx.de> you wrote:
>
> running get_maintainer.pl drops warnings with PERL > 5.22 .
> In linux this is fixed though above commit.
ACK.
> But ... I get differences when running the python script:
So the Python script ...
> ret = subprocess.call(["scripts/get_maintainer.pl", "-f", tmp])
...basically does the equivalent of running
scripts/get_maintainer.pl -f <directory>/<file>
on the command line.
> and comparing the output from it, based on the original
> u-boot code and the code with this patch ...
What exactly do you mean by "I get differences"? What are the used
values for "directory" and "file" in your test case, and which exact
differences do you get?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Don't try to outweird me, three-eyes. I get stranger things than you
free with my breakfast cereal."
- Zaphod Beeblebrox in "Hitchhiker's Guide to the Galaxy"
next prev parent reply other threads:[~2016-01-07 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 12:45 [U-Boot] [RFC v2 PATCH] get_maintainer: fix perl 5.22/5.24 deprecated/incompatible "\C" use Heiko Schocher
2016-01-07 16:13 ` Wolfgang Denk [this message]
2016-01-08 5:53 ` Heiko Schocher
2016-01-09 3:35 ` [U-Boot] [U-Boot, RFC, v2] " Tom Rini
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=20160107161359.5ED03380311@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.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