From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: jan.kratochvil@redhat.com, drow@false.org, amodra@gmail.com,
brobecker@gnat.com, muller@sourceware.org, nickc@redhat.com,
macro@linux-mips.org, binutils@sourceware.org
Subject: Re: [PATCH] readline/util.c: use '%d' instead of 'ld' to avoid compiling warning
Date: Fri, 30 May 2014 17:02:00 -0000 [thread overview]
Message-ID: <5388B9AB.2060207@gmail.com> (raw)
On 05/30/2014 04:27 PM, Pedro Alves wrote:
> On 05/30/2014 03:50 AM, Chen Gang wrote:
>
>> If we have a tool to tell members (especially new members) the related
>> mailing addresses (e.g. "scripts/get_maintainer.pl" under Linux kernel
>> and/or Qemu), that will be cool!
>
> I agree. If you'd like to contribute one, it'll be gladly accepted.
> The information can currently be found in the MAINTAINERS files
> in the several directories in the tree.
>
I am glad to. I am not quite familiar with perl, but it is not the
excuse to let myself stop -- I shall try.
At present, I am scanning binutils for all compiling warnings, and try
to fix them. I guess I need about 1-2 month (I am not quite familiar
with binutils, either have no enough free time for it).
So may I finish scanning warnings, then try "get_maintainers.pl"? (also
welcome any members to scan warnings and/or try "get_maintainers.pl")
[...]
Thanks.
--
Chen Gang
Open, share and attitude like air, water and life which God blessed
next reply other threads:[~2014-05-30 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 17:02 Chen Gang [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-30 0:11 Chen Gang
2014-05-30 2:15 ` Alan Modra
2014-05-30 2:22 ` Alan Modra
2014-05-30 2:28 ` Chen Gang
2014-05-30 2:50 ` Chen Gang
2014-05-30 8:27 ` Pedro Alves
[not found] ` <87lhtj7han.fsf@igel.home>
2014-05-30 16:43 ` Chen Gang
2014-09-15 11:14 ` Chen Gang
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=5388B9AB.2060207@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=brobecker@gnat.com \
--cc=drow@false.org \
--cc=jan.kratochvil@redhat.com \
--cc=macro@linux-mips.org \
--cc=muller@sourceware.org \
--cc=nickc@redhat.com \
--cc=palves@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).