From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: cbiesinger@google.com, gdb@sourceware.org
Subject: Re: Renaming .c files to .cc?
Date: Wed, 11 Dec 2019 16:35:00 -0000 [thread overview]
Message-ID: <83sglqakhg.fsf@gnu.org> (raw)
In-Reply-To: <617317be-2567-fd53-135d-8ed391ae1a86@redhat.com> (message from Pedro Alves on Wed, 11 Dec 2019 10:59:07 +0000)
> From: Pedro Alves <palves@redhat.com>
> Date: Wed, 11 Dec 2019 10:59:07 +0000
>
> IMO, renaming the files has a disproportionate cost/benefit ratio.
> I'm not terribly opposed, but I'm in the "prefer not" camp.
FWIW, I'm in the same camp (although my opinion's weight is much lower
than Pedro's, as I get/need to work with GDB's Git much less than he
does).
prev parent reply other threads:[~2019-12-11 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 22:19 Christian Biesinger via gdb
2019-12-11 0:42 ` Luis Machado
2019-12-11 1:27 ` Christian Biesinger via gdb
2019-12-11 1:33 ` Luis Machado
2019-12-11 2:24 ` Simon Marchi
2019-12-11 3:32 ` Eli Zaretskii
2019-12-11 23:00 ` Christian Biesinger via gdb
2019-12-12 6:17 ` Eli Zaretskii
2019-12-14 18:20 ` Christian Biesinger via gdb
2019-12-11 10:59 ` Pedro Alves
2019-12-11 16:35 ` Eli Zaretskii [this message]
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=83sglqakhg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cbiesinger@google.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.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).