From: Chris Metcalf <cmetcalf@tilera.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: <libc-ports@sourceware.org>, David Miller <davem@davemloft.net>,
Carlos O'Donell <carlos@redhat.com>, <vapier@gentoo.org>
Subject: Re: [PATCH] tile: default to little-endian in bits/endian.h
Date: Sat, 15 Jun 2013 18:55:00 -0000 [thread overview]
Message-ID: <51BCB8A1.2000707@tilera.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1306151720150.18771@digraph.polyomino.org.uk>
On 6/15/2013 1:21 PM, Joseph S. Myers wrote:
> Is there a reason this went on 2.15 and 2.16 branches but not 2.17? We
> don't have a specific policy about keeping the fixes on each branch a
> superset of those on the previous one, but I'd think doing so is generally
> a good idea....
I'm waiting for David's ack as 2.17 maintainer. I got Carlos's for 2.15 (and thus I figured, implicitly 2.16). It seems pretty uncontroversial, but perhaps I should have held off until I had all the maintainers' acks?
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2013-06-15 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 20:57 Chris Metcalf
2013-06-13 2:53 ` Mike Frysinger
2013-06-13 14:26 ` Carlos O'Donell
2013-06-15 17:21 ` Joseph S. Myers
2013-06-15 18:55 ` Chris Metcalf [this message]
2013-06-19 16:36 ` Chris Metcalf
2013-06-19 19:21 ` David Miller
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=51BCB8A1.2000707@tilera.com \
--to=cmetcalf@tilera.com \
--cc=carlos@redhat.com \
--cc=davem@davemloft.net \
--cc=joseph@codesourcery.com \
--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).