From: Roland McGrath <roland@redhat.com>
To: Andreas Schwab <schwab@redhat.com>
Cc: libc-hacker@sourceware.org
Subject: Re: [PATCH] Document M_PERTURB
Date: Tue, 27 Jul 2010 09:32:00 -0000 [thread overview]
Message-ID: <20100727093207.65BBE400DD@magilla.sf.frob.com> (raw)
In-Reply-To: Andreas Schwab's message of Tuesday, 27 July 2010 11:13:29 +0200 <m3fwz5nv7q.fsf@hase.home>
> Roland McGrath <roland@redhat.com> writes:
>
> > I think it should also say "... depending on the low-order byte of
> > this value," so nobody can think that passing in more than 8 bits has
> > any effect.
>
> Depends on how much of it is considered an implementation detail.
True. Perhaps just say "some low-order bits of this parameter".
prev parent reply other threads:[~2010-07-27 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 14:37 Andreas Schwab
2010-07-26 20:01 ` Roland McGrath
2010-07-26 20:17 ` Jakub Jelinek
2010-07-27 9:13 ` Andreas Schwab
2010-07-27 9:32 ` Roland McGrath [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=20100727093207.65BBE400DD@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=libc-hacker@sourceware.org \
--cc=schwab@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 read-only IMAP folder(s) and NNTP newsgroup(s).