From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Prevent source file errors in --batch-silent mode
Date: Sat, 03 May 2008 21:48:00 -0000 [thread overview]
Message-ID: <20080503205602.GB22704@caradoc.them.org> (raw)
In-Reply-To: <1209846868.7034.96.camel@localhost.localdomain>
I don't think we should have this discussion again. It's been had
plenty of times in the past; if you want to restart it send me some
mail off-list and I'll answer there. I am completely convinced that
CVS->Subversion is a reasonable migration for the src repository
and that CVS->distributed VC is not.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-05-03 20:56 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
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 [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=20080503205602.GB22704@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.com \
--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