Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: Rob Quill <rob.quill@gmail.com>
Cc: Markus Deuling <deuling@de.ibm.com>, gdb@sourceware.org
Subject: Re: Scope Checking Patch
Date: Mon, 11 Jun 2007 10:59:00 -0000	[thread overview]
Message-ID: <466D2B04.7040304@st.com> (raw)
In-Reply-To: <baf6008d0706110241m12343d27p4fba7cdeb07f9f1e@mail.gmail.com>

Rob Quill wrote:
> Thanks. I tried this, but I ended up with a 214MB diff file. I'm not
> sure why this is, as I did a make distclean on both copies, I think it
> may be due to the testsuite results not having been cleaned or
> something. Does anyone have any ideas what to do?

Don't build in your source tree. As you discovered it is really 
inconvenient.

Instead, put all the object files in a second directory alongside your 
src directory:

mkdir objdir
cd objdir
../src/configure
make

This way the sources are not polluted* and the diff will be much cleaner.

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.

Hope that helps,

Andrew

* There are some files, such as .info files, which get written back to 
the source tree.


  parent reply	other threads:[~2007-06-11 10:59 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 [this message]
2007-06-11 11:17       ` Nick Roberts
2007-06-11 16:03       ` Daniel Jacobowitz

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=466D2B04.7040304@st.com \
    --to=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