From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Guillem Jover <guillem@hadrons.org>
Cc: Mike Frysinger <vapier@gentoo.org>, libc-ports@sourceware.org
Subject: Re: [PATCH ports] Use __unused0 instead of __unused for user visible struct members
Date: Wed, 04 Jan 2012 11:57:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1201041155320.1721@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20120104071225.GA29510@gaara.hadrons.org>
On Wed, 4 Jan 2012, Guillem Jover wrote:
> The patch seems to have arrived now on the libc-alpha list. In any
> case I don't see the harm in applying this one to the ports tree?
In general, textual differences (including whitespace) between libc and
ports versions of a file should be limited to those that genuinely result
from differences between the architectures, kernel ports, etc.; a cleanup
is applied to ports versions only after it is applied to the libc
versions.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-01-04 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 3:19 Guillem Jover
2012-01-02 6:06 ` Mike Frysinger
2012-01-04 7:12 ` Guillem Jover
2012-01-04 11:57 ` Joseph S. Myers [this message]
2012-01-09 5:35 ` Guillem Jover
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=Pine.LNX.4.64.1201041155320.1721@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=guillem@hadrons.org \
--cc=libc-ports@sourceware.org \
--cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).