From: Michal Marek <mmarek@suse.cz>
To: cody <cody@linux.vnet.ibm.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig: allow long lines in config file
Date: Fri, 13 Jul 2012 22:39:01 +0200 [thread overview]
Message-ID: <50008765.30905@suse.cz> (raw)
In-Reply-To: <50006933.4000004@linux.vnet.ibm.com>
Dne 13.7.2012 20:30, cody napsal(a):
> Do we have any strict standards for what is and is not portable?
We don't. I only checked the existing userspace code and except for
perf, there is no other usage of getline().
> (I'm aware 'getline' was only added to posix ~4 years ago in 2008).
Ah, good to know. Nevetheless, let's stay conservative for some more
time. Thanks for sending the updated patch, btw.
Michal
prev parent reply other threads:[~2012-07-13 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 23:47 [PATCH] kconfig: allow long lines in config file cody
2012-07-13 13:07 ` Michal Marek
2012-07-13 18:27 ` [PATCH v2] " cody
2012-07-13 20:54 ` Michal Marek
2012-07-13 18:30 ` [PATCH] " cody
2012-07-13 20:39 ` Michal Marek [this message]
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=50008765.30905@suse.cz \
--to=mmarek@suse.cz \
--cc=cody@linux.vnet.ibm.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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