From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: FYI: small updates on GDB Coding Style wiki
Date: Thu, 04 Dec 2014 17:15:00 -0000 [thread overview]
Message-ID: <54809699.9010107@redhat.com> (raw)
In-Reply-To: <20141130063649.GA4882@adacore.com>
On 11/30/2014 06:36 AM, Joel Brobecker wrote:
> Hello,
>
> Just FYI - I merged my old "GDB Coding Style Cheat Sheet" wiki page
> into the official "GDB C Coding Standard" page, and deleted mine
> afterwards. Since the wiki is now the official repository for
> documenting our coding standards, I didn't the reason for keeping
> my own page. While doing so, I reformatted a bit the original page,
> doing the following:
> - Added a Table of Contents;
> - used subsections to plit each rule or set of rule;
>
> The objectives where to make it easier to navigate the document when
> in search of a specific rule. I also wanted to separte each rule more
> so that one small but important rule does not get drown between other
> rules, and therefore missed.
Thanks Joel.
Pedro Alves
prev parent reply other threads:[~2014-12-04 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 6:36 Joel Brobecker
2014-12-04 17:15 ` Pedro Alves [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=54809699.9010107@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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).