From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dje@google.com, gdb-patches@sourceware.org,
brobecker@adacore.com, ken@linux.vnet.ibm.com,
tromey@redhat.com, pedro@codesourcery.com
Subject: Re: [doc RFA] Switch to GCC coding style [Re: [patch] initial OpenCL C language support]
Date: Mon, 08 Nov 2010 12:50:00 -0000 [thread overview]
Message-ID: <20101108124942.GA29408@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <8339rj5y7z.fsf@gnu.org>
On Tue, 02 Nov 2010 20:20:32 +0100, Eli Zaretskii wrote:
> Are you submitting this for doc review, or will we discuss the issue
> first?
I thought about it as a quick fix as currently the code follows different
rules ("!" - GCC) than what states gdbint.texinfo ("! " - GNU). At least
Pedro says "We tend to follow these already".
> I don't think this is enough, sorry. The GCC Conventions mention a
> lot of details that are utterly inapplicable to GDB. The exceptions
> you mention are just a drop in that sea. What about references to
> ERROR_MARK, RTL, --param arguments, what about fastjar and boehm-gc?
> And those are just a few random examples.
>
> On balance, I think we should simply have our own coherent document.
Yes, it would be better. But I am not going to spend the time on it myself.
> Any other way, we will just confuse potential contributors:
They are already confused now (at least I have been confused by "!" vs. "! "
so far myself) and IMO the proposed patch reduces the confusion.
> To say nothing of the fact that they will now have to read two documents
> instead of 1.
3 instead of 2 (besides GNU Coding Standards and gdbint.texinfo Coding
Standards proposing also GCC Coding Conventions).
Regards,
Jan
next prev parent reply other threads:[~2010-11-08 12:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 17:21 [patch] initial OpenCL C language support Ken Werner
2010-10-25 22:41 ` Tom Tromey
2010-10-26 13:05 ` Ken Werner
2010-10-26 13:44 ` Tom Tromey
2010-10-26 16:02 ` Ken Werner
2010-10-26 17:49 ` Eli Zaretskii
2010-10-26 19:58 ` Joel Brobecker
2010-10-26 20:03 ` Joel Brobecker
2010-10-27 13:36 ` Ken Werner
2010-11-02 19:23 ` Joel Brobecker
2010-11-03 13:03 ` Ken Werner
2010-11-03 15:27 ` Joel Brobecker
2010-11-04 15:39 ` Ken Werner
2010-11-04 17:48 ` Eli Zaretskii
2010-11-05 14:21 ` Ken Werner
2010-11-05 14:39 ` Ken Werner
2010-10-27 19:04 ` Jan Kratochvil
2010-10-27 19:21 ` Pedro Alves
2010-10-27 21:01 ` Ken Werner
2010-11-02 16:52 ` [doc RFA] Switch to GCC coding style [Re: [patch] initial OpenCL C language support] Jan Kratochvil
2010-11-02 17:04 ` Doug Evans
2010-11-02 17:23 ` Jan Kratochvil
2010-11-02 17:29 ` Doug Evans
2010-11-02 19:21 ` Eli Zaretskii
2010-11-02 19:29 ` Joel Brobecker
2010-11-08 12:50 ` Jan Kratochvil [this message]
2010-11-08 16:11 ` Joel Brobecker
2010-11-08 16:38 ` Mark Kettenis
2010-11-08 16:43 ` Joel Brobecker
2010-11-08 16:54 ` Pedro Alves
2010-11-08 18:36 ` Joel Brobecker
2010-11-02 18:01 ` Joel Brobecker
2010-11-02 18:10 ` [doc RFA] Switch to GCC coding style Jan Kratochvil
2010-11-02 18:20 ` Doug Evans
2010-11-02 18:58 ` Joel Brobecker
2010-11-02 19:19 ` Doug Evans
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=20101108124942.GA29408@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ken@linux.vnet.ibm.com \
--cc=pedro@codesourcery.com \
--cc=tromey@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).