From: Philip Harvey <harveyp@coventry.ac.uk>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: replacing strtok() with strsep()
Date: 27 Dec 2001 21:52:41 +0000 [thread overview]
Message-ID: <1009489962.8806.3.camel@arrakis> (raw)
In-Reply-To: <Pine.LNX.4.33.0112272211480.15706-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.33.0112272211480.15706-100000@Appserv.suse.de>
On Thu, 2001-12-27 at 21:14, Dave Jones wrote:
> Someone (I forget who) took a run-through about 6 months back.
> AFAIK, they still sit in the last -ac tree, and not all (if any) of them
> got merged. If I get bored/desperate for patches to merge, I'll resurrect
> them for -dj. There are some other bits I keep meaning to dig out of
> Alans old tree, so if you decide to go do this and just bring these in
> sync for 2.5, I've no problem putting them in -dj until such a time
> for them to get maintainer-review/testing/merging.
>
> The kernel-janitor list archives should hold copies of some of them.
> (See the sf page for details)
theres some individual patches for single files dating back a while, but
nothing comprehensive. i'll start tieing things together for 2.5,
perhaps starting with the fs/ subtree which nobody seems to have
touched in a while. it would be nice to declare 2.5 a strtok free zone.
most people are using strtok to seperate options, using exactly the same
syntax. what are your thoughts on creating a strsep() macro to replace
them?
-phil
prev parent reply other threads:[~2001-12-27 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-27 21:04 replacing strtok() with strsep() Philip Harvey
2001-12-27 21:14 ` Dave Jones
2001-12-27 21:52 ` Philip Harvey [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=1009489962.8806.3.camel@arrakis \
--to=harveyp@coventry.ac.uk \
--cc=davej@suse.de \
--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