From: Kevin Buettner <kevinb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>, gdb@sources.redhat.com
Subject: Re: gdb_indent vs. dwarf2read
Date: Mon, 27 Jan 2003 17:11:00 -0000 [thread overview]
Message-ID: <1030127171106.ZM20142@localhost.localdomain> (raw)
In-Reply-To: Daniel Jacobowitz <drow@mvista.com> "gdb_indent vs. dwarf2read" (Jan 26, 10:11pm)
On Jan 26, 10:11pm, Daniel Jacobowitz wrote:
> What do people think about adding "-T bfd -T asection" to gdb_indent.sh?
I think it makes sense.
> [I'd like to re-indent dwarf2read.c, so I was looking over the results of
> gdb_indent.sh on it before posting the patch. Other churn: structs moved
> from two spaces indented to the left column, which matches the general style
> in GDB; and comments like:
> 1) foo
> bar
> reindented to
> 1) foo
> bar
> . Should we slavishly obey GNU indent in this, or should I reformat the
> comments by hand before posting the reindentation patch?]
The problem with reformatting the comments (or anything else) by hand
is that someone else who runs GNU indent probably won't do the same
hand formatting. If there's something you don't want indent to touch,
use /* *INDENT-OFF* */ (and later on, at the right point, /* *INDENT-ON* */.
Kevin
next prev parent reply other threads:[~2003-01-27 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 3:10 Daniel Jacobowitz
2003-01-27 17:11 ` Kevin Buettner [this message]
2003-01-27 17:30 ` Andrew Cagney
2003-01-27 17:43 ` Daniel Jacobowitz
2003-01-27 19:05 ` Andrew Cagney
2003-01-27 19:17 ` Daniel Jacobowitz
2003-01-27 20:44 ` Andrew Cagney
2003-01-27 20:02 ` breakpoints jacques
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=1030127171106.ZM20142@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.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