From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH] gfs2: better code for translating characters
Date: Tue, 14 Aug 2007 11:31:13 +0100 [thread overview]
Message-ID: <1187087473.8765.846.camel@quoit> (raw)
In-Reply-To: <46C08843.8010302@zytor.com>
Hi,
On Mon, 2007-08-13 at 09:35 -0700, H. Peter Anvin wrote:
> rae l wrote:
> > On 8/13/07, H. Peter Anvin <hpa@zytor.com> wrote:
> >> You seem to have confused modern compiled C with an old BASIC interpreter.
> >>
> >> Consider the code in point:
> >>
> >> - while ((table = strchr(sdp->sd_table_name, '/')))
> >> + table = sdp->sd_table_name;
> >> + while ((table = strchr(table, '/')))
> >> *table = '_';
> > Sorry, I just mean for call to strchr, things are different,
> > especially for multiple '/' chars appeared.
>
> Things are different only for multiple '/' chars. In that case, the
> latter form is better, in the former case, there is no difference.
>
> So it doesn't matter. One is unambiguously better.
>
> -hpa
I agree, so I've applied the patch. Thanks Denis,
Steve.
next prev parent reply other threads:[~2007-08-14 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11869741183677-git-send-email-crquan@gmail.com>
[not found] ` <91b13c310708122008w27b86359n5b135df3e229e616@mail.gmail.com>
2007-08-13 4:27 ` [Cluster-devel] Re: [PATCH] gfs2: better code for translating characters H. Peter Anvin
[not found] ` <91b13c310708122206v5e4023f2w7464611a96ae67d9@mail.gmail.com>
2007-08-13 5:51 ` H. Peter Anvin
2007-08-13 9:19 ` rae l
2007-08-13 16:35 ` H. Peter Anvin
2007-08-14 10:31 ` Steven Whitehouse [this message]
2007-08-14 10:25 ` Steven Whitehouse
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=1187087473.8765.846.camel@quoit \
--to=swhiteho@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 NNTP newsgroup(s).