From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Prevent source file errors in --batch-silent mode
Date: Sat, 03 May 2008 06:23:00 -0000 [thread overview]
Message-ID: <1209790046.7034.79.camel@localhost.localdomain> (raw)
In-Reply-To: <20080502140633.GF29202@caradoc.them.org>
On Fri, 2008-05-02 at 10:06 -0400, Daniel Jacobowitz wrote:
> On Fri, May 02, 2008 at 03:00:15PM +0100, Andrew STUBBS wrote:
> > I think I've been spoilt by makefiles that generate the dependencies
> > automatically. :)
>
> Yeah. The next time there's a break in the furious feature
> development GDB's seen lately, and I have some time for
> infrastructure work, that is on my list.
Nice.
> The other items on that list are "move to bugzilla"
Nice!
> and "switch src to svn 1.5 when it is released", FWIW.
Hum... any reason in particular for that? It seems everyone keeps their
own version of the GDB source tree. Using a distributed VCS would ease
that work and benefit everybody...
Besides, there are talks of moving gcc to a DVCS also, no?
Or is this flamebait and I've just bitten? :-)
--
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center
next prev parent reply other threads:[~2008-05-03 4:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 19:34 Andrew STUBBS
2008-04-28 19:02 ` Andrew STUBBS
2008-05-01 20:34 ` Daniel Jacobowitz
2008-05-02 11:35 ` Andrew STUBBS
2008-05-02 13:46 ` Daniel Jacobowitz
2008-05-02 14:03 ` Andrew STUBBS
2008-05-02 14:10 ` Daniel Jacobowitz
2008-05-03 6:23 ` Thiago Jung Bauermann [this message]
2008-05-03 14:26 ` Christopher Faylor
2008-05-03 20:56 ` Thiago Jung Bauermann
2008-05-03 15:33 ` Daniel Jacobowitz
2008-05-03 20:54 ` Thiago Jung Bauermann
2008-05-03 21:48 ` 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=1209790046.7034.79.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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