From: David Miller <davem@davemloft.net>
To: roland@hack.frob.com
Cc: libc-alpha@sourceware.org, libc-ports@sourceware.org, rth@twiddle.net
Subject: Re: foo.s
Date: Sat, 19 May 2012 22:38:00 -0000 [thread overview]
Message-ID: <20120519.183813.1716277143511006516.davem@davemloft.net> (raw)
In-Reply-To: <20120519051409.CE5002C083@topped-with-meat.com>
From: Roland McGrath <roland@hack.frob.com>
Date: Fri, 18 May 2012 22:14:09 -0700 (PDT)
>> It looks like only Alpha and HPPA have foo.s files any longer.
>
> Then libc-ports is the place that needs to hear the request (CC'd).
>
>> I did a quick scan over them in the glibc-ports tree and I see no
>> reason why changing them all over to foo.S would break things.
>
> I can't imagine how it would. (Actually I can, if there are foo.s files
> using identifiers that $(compile-command.S) predefines. But it doesn't
> seem inordinately likely--who would be as foolish as i686?)
Carlos just took care of HPPA and therefore only Alpha is left.
Richard, could I trouble you do do the "foo.s --> foo.S" renames
for Alpha and do a test build? I'd really appreciate it.
Once that's taken care of I'll post and commit the mainline patch
to get rid of the .s prefix rules.
next prev parent reply other threads:[~2012-05-19 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120519.003852.1167279910667363123.davem@davemloft.net>
2012-05-19 5:14 ` foo.s Roland McGrath
2012-05-19 22:38 ` David Miller [this message]
2012-05-20 19:35 ` foo.s Richard Henderson
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=20120519.183813.1716277143511006516.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=roland@hack.frob.com \
--cc=rth@twiddle.net \
/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).