Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
	        Dave Korn <dave.korn.cygwin@googlemail.com>,
	binutils@sourceware.org,         gcc-patches@gcc.gnu.org,
	gdb-patches@sources.redhat.com
Subject: Re: [PATCH 4/N] The big bump
Date: Tue, 18 Aug 2009 20:34:00 -0000	[thread overview]
Message-ID: <m3ws50dheo.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090818191404.GB30961__32944.9385325008$1250622877$gmane$org@gmx.de> 	(Ralf Wildenhues's message of "Tue, 18 Aug 2009 21:14:04 +0200")

>>>>> "Ralf" == Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:

Ralf> Thanks guys.  Does anyone have an up to date git clone of the full src
Ralf> tree?  If not, are there any volunteers to set one up, or can I bribe
Ralf> one?

I don't think there is one; AFAIK there are only git trees for a couple
parts of src.

Ralf> - parts of itcl with 2.61,
Ralf> - parts of tk and parts of tcl with 2.60a,

My understanding is that gdb changes can be made without worrying about
the consequence to the Insight bits, because Insight is not "official"
in some way.

I would suggest that this also applies to build infrastructure -- IMO it
would be ok for you to move forward with the main parts and fix this up
later.

Ralf> This patch series is almost ready to go otherwise (expect to be able to
Ralf> commit this weekend), and it'd be sad to see it hostage of the lesser
Ralf> tightly maintained part of the tree.

FWIW, I tend to agree.  I know this sort of change is very difficult to
get in and I think it would be worthwhile to bend the rules a little to
make it simpler for you.

Tom


  parent reply	other threads:[~2009-08-18 19:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A86E723.3000602@gmail.com>
     [not found] ` <Pine.LNX.4.64.0908151616540.28033@digraph.polyomino.org.uk>
2009-08-18 19:21   ` Ralf Wildenhues
2009-08-18 19:57     ` Paolo Bonzini
2009-08-18 23:39     ` Dave Korn
     [not found] ` <20090818191404.GB30961__32944.9385325008$1250622877$gmane$org@gmx.de>
2009-08-18 20:34   ` Tom Tromey [this message]
2009-08-24 17:56     ` Christopher Faylor

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=m3ws50dheo.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=binutils@sourceware.org \
    --cc=dave.korn.cygwin@googlemail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=joseph@codesourcery.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