From: Richard Guenther <richard.guenther@gmail.com>
To: Nicola Pero <nicola.pero@meta-innovation.com>
Cc: "gcc-patches@gnu.org" <gcc-patches@gnu.org>
Subject: Re: Rename attribs.c to attributes.c
Date: Wed, 22 Jun 2011 18:15:00 -0000 [thread overview]
Message-ID: <BANLkTi==fg1tk7CKPwgCoTiwEqM1ptcz8Q@mail.gmail.com> (raw)
In-Reply-To: <1308763134.873631959@www2.webmail.us>
On Wed, Jun 22, 2011 at 7:18 PM, Nicola Pero
<nicola.pero@meta-innovation.com> wrote:
> This patch renames attribs.c to attributes.c.
>
> I can only imagine the short "attribs.c" name was picked many years ago
> due to filename restrictions on certain systems ? Nowadays, it seems
> that we already have plenty of long filenames inside GCC, so there is
> no reason to use cryptic, newbie-unfriendly, shortened names for files. ;-)
>
> Bootstrapped with c,c++,objc,obj-c++,lto,java,fortran,ada,go on Linux i686.
>
> OK to commit ?
Huh, I see no reason for this rename. It'll just make patches across
releases harder.
Richard.
> Thanks
>
> In gcc/:
> 2011-06-22 Nicola Pero <nicola.pero@meta-innovation.com>
>
> * attribs.c: Renamed to attributes.c.
> * Makefile.in: Changed all occurrences of attribs.c and attribs.o
> to attributes.c and attributes.o.
> * langhooks.h: Updated comments to refer to attributes.c instead
> of attribs.c.
> * plugin.h: Likewise.
> * tree.h: Likewise.
>
> In gcc/ada/:
> 2011-06-22 Nicola Pero <nicola.pero@meta-innovation.com>
>
> * gcc-interface/Make-lang.in (ADA_BACKEND): Renamed attribs.o to
> attributes.o.
>
> In gcc/cp/:
> 2011-06-22 Nicola Pero <nicola.pero@meta-innovation.com>
>
> * Make-lang.in (CXX_C_OBJS): Renamed attribs.o to attributes.o.
>
> In gcc/fortran/:
> 2011-06-22 Nicola Pero <nicola.pero@meta-innovation.com>
>
> * Make-lang.in (f951$(exeext)): Replaced attribs.o with
> attributes.o.
>
> In gcc/go/:
> 2011-06-22 Nicola Pero <nicola.pero@meta-innovation.com>
>
> * Make-lang.in (go1$(exeext)): Rename attribs.o to attributes.o.
>
> In gcc/java/:
> 2011-06-22 Nicola Pero <nicola.pero@meta-innovation.com>
>
> * Make-lang.in (jc1$(exeext)): Renamed attribs.o to attributes.o.
>
> In gcc/lto/:
> 2011-06-22 Nicola Pero <nicola.pero@meta-innovation.com>
>
> * Make-lang.in (LTO_OBJS): Renamed attribs.o to attributes.o
>
next prev parent reply other threads:[~2011-06-22 18:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 17:58 Nicola Pero
2011-06-22 18:15 ` Richard Guenther [this message]
2011-06-22 18:55 ` Nicola Pero
2011-06-22 18:56 ` Richard Guenther
2011-06-22 19:16 ` Andrew MacLeod
2011-06-22 19:53 ` Basile Starynkevitch
2011-06-22 23:54 ` Joseph S. Myers
2011-06-22 19:33 ` Joseph S. Myers
2011-06-22 19:56 ` Basile Starynkevitch
2011-06-22 20:58 ` Diego Novillo
2011-06-22 21:48 ` Basile Starynkevitch
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='BANLkTi==fg1tk7CKPwgCoTiwEqM1ptcz8Q@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gnu.org \
--cc=nicola.pero@meta-innovation.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).