From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: Rob Quill <rob.quill@gmail.com>,
Markus Deuling <deuling@de.ibm.com>,
gdb@sourceware.org
Subject: Re: Scope Checking Patch
Date: Mon, 11 Jun 2007 16:03:00 -0000 [thread overview]
Message-ID: <20070611155654.GA10916@caradoc.them.org> (raw)
In-Reply-To: <466D2B04.7040304@st.com>
On Mon, Jun 11, 2007 at 11:59:16AM +0100, Andrew STUBBS wrote:
> Also, like Markus said, always use context or unified diffs. Ordinary diff
> output isn't nearly so useful. I'd also suggest using the -p option - it adds a
> procedure name to each hunk - entirely cosmetic, but nice to
> have.
Yes. Rob, please use diff -up, and send patches to gdb-patches -
very little should be cross-posted to both lists. Thanks.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-06-11 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 20:54 Rob Quill
2007-06-10 20:55 ` Rob Quill
2007-06-11 17:12 ` Jim Blandy
2007-06-11 17:31 ` Rob Quill
2007-06-11 8:31 ` Markus Deuling
2007-06-11 9:41 ` Rob Quill
2007-06-11 10:58 ` Markus Deuling
2007-06-11 10:59 ` Andrew STUBBS
2007-06-11 11:17 ` Nick Roberts
2007-06-11 16:03 ` Daniel Jacobowitz [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=20070611155654.GA10916@caradoc.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.com \
--cc=deuling@de.ibm.com \
--cc=gdb@sourceware.org \
--cc=rob.quill@gmail.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