From: Simon Marchi <simon.marchi@ericsson.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Import strchrnul from gnulib and use it
Date: Thu, 28 Jan 2016 16:16:00 -0000 [thread overview]
Message-ID: <56AA3EE5.5050705@ericsson.com> (raw)
In-Reply-To: <86r3h1pud0.fsf@gmail.com>
On 16-01-28 11:00 AM, Yao Qi wrote:
> If we have dependent modules, such as rawmemchr, we need to list them here
> explicitly too.
Is there a reason for this? If one day we decide that we don't want strchrnul
anymore, we are probably going to forget about rawmemchr, and it will still be
imported even though it's not used.
If it's a policy that has been discussed before, I have no problem adding it.
I would just like to understand.
Thanks,
Simon
next prev parent reply other threads:[~2016-01-28 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 21:04 Simon Marchi
2016-01-27 21:43 ` Sergio Durigan Junior
2016-01-28 12:00 ` Pedro Alves
2016-01-28 15:34 ` Simon Marchi
2016-01-28 16:00 ` Yao Qi
2016-01-28 16:16 ` Simon Marchi [this message]
2016-01-28 17:44 ` Yao Qi
2016-01-28 18:51 ` Simon Marchi
2016-01-30 18:01 ` Matt Rice
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=56AA3EE5.5050705@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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).