Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Andrew STUBBS <andrew.stubbs@st.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: automatic dependency tracking
Date: Sat, 02 Aug 2008 20:34:00 -0000	[thread overview]
Message-ID: <1217709229.30616.8.camel@localhost.localdomain> (raw)
In-Reply-To: <m3zlny15fb.fsf@fleche.redhat.com>

On Thu, 2008-07-31 at 08:42 -0600, Tom Tromey wrote:
> >>>>> "Andrew" == Andrew STUBBS <andrew.stubbs@st.com> writes:
> Here's a new version of the patch.  This one is updated to cvs trunk
> (as of a few minutes ago) and I tested it with depmode=gcc (bypassing
> the gcc3 special case).
> 
> You were correct, depmode was not set.  This patch fixes that.

I just thought I'd convert my nod when reading this thread into an
e-mail.

I think this is a great idea and will relieve a burden from the GDB
developer, not only by eliminating the need for updating the Makefile
for each added or removed #include, but (even more so) by eliminating a
number of conflicts when you have to maintain a patchset (like I'm doing
with the Python series, and Pedro is doing with the non-stop debugging
series). It also relieves a burden from the patch reviewer (has the
developer correctly updated the Makefile?).
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


  reply	other threads:[~2008-08-02 20:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 22:14 Tom Tromey
2008-07-30 17:53 ` Pedro Alves
2008-07-30 19:12   ` Tom Tromey
2008-07-31 18:51     ` Pedro Alves
2008-07-31 10:48 ` Andrew STUBBS
2008-07-31 12:16   ` Tom Tromey
2008-07-31 14:43   ` Tom Tromey
2008-08-02 20:34     ` Thiago Jung Bauermann [this message]
2008-08-07  5:50 ` Ralf Wildenhues
2008-08-07 13:47   ` Tom Tromey
2008-08-07 13:53     ` Daniel Jacobowitz
2008-08-07 19:17     ` Ralf Wildenhues
2008-08-07 20:07       ` Tom Tromey
2008-08-07 20:46         ` Ralf Wildenhues
2008-08-07 20:51           ` Tom Tromey
2008-08-07 20:17       ` Daniel Jacobowitz
2008-08-07 20:22         ` Tom Tromey
2008-08-07 20:46           ` Ralf Wildenhues
2008-08-07 20:49             ` Tom Tromey
2008-08-07 20:59       ` Daniel Jacobowitz
2008-08-07 22:51         ` Ralf Wildenhues
2008-08-08 14:37           ` Thiago Jung Bauermann
2008-08-08 15:18             ` Tom Tromey
2008-08-08 15:24               ` Ralf Wildenhues
2008-08-08 17:27                 ` Tom Tromey
2008-08-08 17:35               ` Daniel Jacobowitz
2008-08-07 17:09   ` Tom Tromey
2008-08-07 19:23     ` Ralf Wildenhues

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=1217709229.30616.8.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=andrew.stubbs@st.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=tromey@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