From: Chris Wedgwood <cw@f00f.org>
To: Olaf Dietsche <olaf.dietsche#list.linux-kernel@t-online.de>
Cc: linux-kernel@vger.kernel.org, trivial@rustcorp.com.au
Subject: Re: [PATCH] 2.5.47: strdup()
Date: Sat, 16 Nov 2002 20:40:39 -0800 [thread overview]
Message-ID: <20021117044039.GA1860@tapu.f00f.org> (raw)
In-Reply-To: <873cq1nfhk.fsf@goat.bogus.local>
On Sun, Nov 17, 2002 at 02:37:27AM +0100, Olaf Dietsche wrote:
> So you like duplicate code? Well, to each his own.
Not at all.
I'm just not sure I like strdup being *easy* to use at it leads to
misuse. Admittedly this is a very poor argument for not having it.
--cw
next prev parent reply other threads:[~2002-11-17 4:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 6:21 [PATCH] 2.5.47: strdup() Olaf Dietsche
2002-11-16 6:25 ` Jeff Garzik
2002-11-16 6:31 ` Andrew Morton
2002-11-16 15:42 ` Olaf Dietsche
2002-11-17 23:32 ` Werner Almesberger
2002-11-18 2:43 ` Olaf Dietsche
2002-11-16 6:41 ` William Lee Irwin III
2002-11-17 0:08 ` Chris Wedgwood
2002-11-17 1:37 ` Olaf Dietsche
2002-11-17 4:40 ` Chris Wedgwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-16 8:48 Peter Kjellerstedt
2002-11-16 15:53 ` Olaf Dietsche
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=20021117044039.GA1860@tapu.f00f.org \
--to=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf.dietsche#list.linux-kernel@t-online.de \
--cc=trivial@rustcorp.com.au \
/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