From: William Lee Irwin III <wli@holomorphy.com>
To: Rusty Trivial Russell <trivial@rustcorp.com.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL] Fix comment in parse_hex_value
Date: Tue, 23 Sep 2003 20:48:58 -0700 [thread overview]
Message-ID: <20030924034858.GI4306@holomorphy.com> (raw)
In-Reply-To: <20030924032926.4485D2C56E@lists.samba.org>
On Wed, Sep 24, 2003 at 12:50:45PM +1000, Rusty Trivial Russell wrote:
> - * Parse the first 8 characters as a hex string, any non-hex char
> + * Parse the first HEX_DIGITS characters as a hex string, any non-hex char
This is good; thanks for catching it. I was over this recently and
should have cleaned it up while I was there.
-- wli
prev parent reply other threads:[~2003-09-24 3:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 2:50 [TRIVIAL] Fix comment in parse_hex_value Rusty Trivial Russell
2003-09-24 3:48 ` William Lee Irwin III [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=20030924034858.GI4306@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--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