From: Ulrich Drepper <drepper@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: libc-hacker@sources.redhat.com
Subject: Re: Fix cast as lvalue in sunrpc
Date: Sun, 08 Feb 2004 18:15:00 -0000 [thread overview]
Message-ID: <40267CA7.4050506@redhat.com> (raw)
In-Reply-To: <je4qu1frw8.fsf@sykes.suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andreas Schwab wrote:
> This fixes the uses of casts as lvalue in the sunrpc code.
Does this change the generated code?
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA â–
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAJnyn2ijCOnn/RHQRAh7jAJ9Gfxlg5VH7UjhKZxhIruv4LvEm+gCgunRu
I4IjvJ7hRpF61a+Gu+WPELI=
=csAe
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-02-08 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 16:41 Andreas Schwab
2004-02-08 18:15 ` Ulrich Drepper [this message]
2004-02-08 18:26 ` Andreas Jaeger
2004-02-08 18:55 ` Ulrich Drepper
2004-02-08 19:11 ` Andreas Schwab
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=40267CA7.4050506@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=schwab@suse.de \
/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).