From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] MI: new timing command
Date: Wed, 03 Jan 2007 22:59:00 -0000 [thread overview]
Message-ID: <20070103225931.GR17935@nevyn.them.org> (raw)
In-Reply-To: <17820.9474.773413.259028@kahikatea.snap.net.nz>
On Thu, Jan 04, 2007 at 10:49:54AM +1300, Nick Roberts wrote:
> > I don't even understand why we're having this conversation. Please
> > follow the coding standard unless you have a good justification not to;
> > that's why we call it the standard. Thanks.
>
> Sure, I didn't say that I wouldn't do it. I'm just waiting for Eli to tell
> me if it works with get_run_time. Meanwhile here's a revised version of
> mi-main.c. I've even made line breaks before, instead of after, operators!
Please... (from gdb/CONTRIBUTE):
o Please read your patch before submitting it.
A patch containing several unrelated changes or
arbitrary reformats will be returned with a request
to re-formatting / split it.
If you're volunteering to fix up formatting in the MI files, go right
ahead; patches which only fix formatting problems are obvious, as long
as you've proofread them. But patches which mix code changes and
formatting changes are pretty much impossible to read. The one you
just posted, for instance, was 40K and had about twenty lines of actual
new code in it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-03 22:59 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-30 8:52 Nick Roberts
2006-12-30 12:09 ` Vladimir Prus
2006-12-30 16:10 ` Eli Zaretskii
2006-12-31 3:26 ` Nick Roberts
2006-12-31 4:26 ` Eli Zaretskii
2006-12-31 6:55 ` Nick Roberts
2006-12-31 15:10 ` Daniel Jacobowitz
2007-01-01 4:11 ` Nick Roberts
2007-01-03 18:01 ` Daniel Jacobowitz
2007-01-03 21:50 ` Nick Roberts
2007-01-03 22:59 ` Daniel Jacobowitz [this message]
2007-01-04 2:50 ` Nick Roberts
2006-12-31 15:33 ` Vladimir Prus
2006-12-30 16:09 ` Eli Zaretskii
2006-12-30 22:10 ` Nick Roberts
2006-12-31 4:22 ` Eli Zaretskii
2006-12-31 4:25 ` Daniel Jacobowitz
2006-12-31 5:18 ` Nick Roberts
2006-12-31 5:49 ` Daniel Jacobowitz
2006-12-31 7:47 ` Nick Roberts
2006-12-31 15:15 ` Daniel Jacobowitz
2006-12-31 15:24 ` Mark Kettenis
2006-12-31 15:39 ` Vladimir Prus
2006-12-31 16:09 ` Mark Kettenis
2006-12-31 16:21 ` Vladimir Prus
2006-12-31 19:29 ` Daniel Jacobowitz
2006-12-31 22:08 ` Eli Zaretskii
2007-01-01 4:24 ` Nick Roberts
2007-01-01 6:06 ` Eli Zaretskii
2007-01-01 4:07 ` Nick Roberts
2007-01-01 5:58 ` Eli Zaretskii
2007-01-01 22:07 ` Nick Roberts
2007-01-02 4:20 ` Eli Zaretskii
2007-01-16 5:57 ` Nick Roberts
2007-01-16 22:17 ` Eli Zaretskii
2007-01-16 22:30 ` Nick Roberts
2007-01-16 23:01 ` Eli Zaretskii
2007-01-20 17:27 ` Eli Zaretskii
2007-01-20 20:58 ` Nick Roberts
2007-01-27 14:53 ` Eli Zaretskii
2007-01-27 15:10 ` Eli Zaretskii
2007-01-27 22:12 ` Nick Roberts
2007-01-27 22:19 ` Nick Roberts
2007-01-27 22:08 ` Nick Roberts
2007-01-28 4:17 ` Eli Zaretskii
2007-01-28 5:31 ` Nick Roberts
2007-02-02 13:33 ` Eli Zaretskii
2007-02-02 23:28 ` Nick Roberts
2007-02-03 11:10 ` Eli Zaretskii
2007-01-01 9:18 ` Nick Roberts
2007-01-01 16:21 ` Daniel Jacobowitz
2006-12-31 15:34 ` Vladimir Prus
2006-12-31 11:58 ` Mark Kettenis
2006-12-31 7:50 ` Nick Roberts
2006-12-31 18:33 ` Vladimir Prus
2007-01-01 4:18 ` Nick Roberts
2006-12-31 22:10 ` 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=20070103225931.GR17935@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=nickrob@snap.net.nz \
/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