From: Kevin Buettner <kevinb@redhat.com>
To: Paul Hilfinger <hilfingr@gnat.com>, ac131313@cygnus.com
Cc: gdb@sources.redhat.com
Subject: Re: More code code dropping
Date: Sat, 08 Dec 2001 07:56:00 -0000 [thread overview]
Message-ID: <1011208155449.ZM11896@ocotillo.lan> (raw)
In-Reply-To: Paul Hilfinger <hilfingr@gnat.com> "Re: More code code dropping" (Dec 8, 3:15am)
On Dec 8, 3:15am, Paul Hilfinger wrote:
> I thought that a diff against the gdb 5.0 release
> was probably most useful. Andrew had suggested a patch against the
> latest, bleeding-edge changes. Since the idea of a diff is to give the
> curious some idea of our changes, it seemed to me that the latter diff would
> show mostly undoings of more recent changes to GDB. If anyone else out
> there has an opinion on this subject, I'd like to hear it.
I think it depends upon what you want. Personally, I'd be interested
in seeing a patch that shows the changes that ACT has made. So the
best candidate for diffing against would be the version of GDB that
you merged with in your most recent merge.
OTOH, a patch against the bleeding edge sources gives us a method of
obtaining your source tree. Personally, I think it'd just be better
for you to drop a tarball someplace if this is what's desired.
As I think about it now, I think a tarball is probably the best
approach anyway. That, along with a pointer to the version of
GDB that you merged against should allow those interested to
do their own diffs in whatever why they want...
Kevin
next prev parent reply other threads:[~2001-12-08 15:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Paul Hilfinger <hilfingr@gnat.com>
2001-11-29 0:59 ` Huge Apple gdb code dropping^H^H^H^H Jason Molenda
2001-11-24 6:24 ` Jason Molenda
2001-11-25 0:39 ` Jason Molenda
2001-11-29 11:12 ` Jason Molenda
2001-11-29 13:34 ` Andrew Cagney
2001-11-25 9:41 ` Andrew Cagney
2001-11-25 9:42 ` Jason Molenda
2001-11-29 13:43 ` Jason Molenda
2001-11-25 9:47 ` Daniel Berlin
2001-11-29 14:15 ` Daniel Berlin
2001-11-29 7:29 ` David Relson
2001-11-24 12:36 ` David Relson
2001-11-29 10:27 ` Stan Shebs
2001-11-25 0:36 ` Stan Shebs
2001-11-29 11:25 ` Jason Molenda
2001-11-25 1:24 ` Jason Molenda
[not found] ` <200112070641.WAA01521@localhost.localdomain>
[not found] ` <3C10E0F3.2010607@cygnus.com>
2001-12-07 7:43 ` More code code dropping Andrew Cagney
2001-12-08 0:17 ` Paul Hilfinger
2001-12-08 7:56 ` Kevin Buettner [this message]
2001-12-08 11:05 ` David Relson
2001-12-08 15:27 ` Andrew Cagney
2001-12-13 5:27 ` Paul N. Hilfinger
2001-12-15 11:32 ` Andrew Cagney
2001-12-08 18:05 ` Jason Molenda
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=1011208155449.ZM11896@ocotillo.lan \
--to=kevinb@redhat.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=hilfingr@gnat.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