From: Joel Brobecker <brobecker@adacore.com>
To: Michael <boost@cyberfiber.org>
Cc: gdb-patches@sourceware.org
Subject: Re: coding conventions
Date: Sun, 03 Jan 2010 03:17:00 -0000 [thread overview]
Message-ID: <20100103031638.GY2788@adacore.com> (raw)
In-Reply-To: <4B3FB999.6010005@cyberfiber.org>
> it was generated using the command 'svn diff > ../boost.diff"
There must be a confusion somewhere. FSF GDB is available only
via either CVS or git. Also, I don't know that GDB has a boost
subdirectory.
> questions on the formatting of new code (conforming standards used at
> gdb-patches@gnu.org):
>
> 1) can lines exceed the 80 character limit?
No.
> 2) should standard indentation be taken as 2 or 4 white spaces?
2 spaces. We also replace blocks of 8 spaces at the beginning of
a line by tabs.
--
Joel
next prev parent reply other threads:[~2010-01-03 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 21:24 Michael
2010-01-03 3:17 ` Joel Brobecker [this message]
2010-01-03 10:34 ` Eli Zaretskii
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=20100103031638.GY2788@adacore.com \
--to=brobecker@adacore.com \
--cc=boost@cyberfiber.org \
--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