Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@redhat.com>
To: Michael Eager <eager@eagercon.com>
Cc: Stan Shebs <shebs@apple.com>, gdb-patches@sources.redhat.com
Subject: Re: Forgot to note
Date: Wed, 11 Oct 2000 12:55:00 -0000	[thread overview]
Message-ID: <m3y9zv6tku.fsf@dan2.cygnus.com> (raw)
In-Reply-To: <39E4B09A.D096436F@eagercon.com>

Michael Eager <eager@eagercon.com> writes:

> Stan Shebs wrote:
> > 
> > Even under an optimistic dwarf2 adoption scenario (dwarf2 still
> > hasn't been standardized for one thing, although it's getting
> > close), the stabs format is going to be with us for at least another
> > five years, so you should plan your hacking so that you can live with
> > the stabs reader for that long.
> 
> FYI, the current plan is to consider all of the proposals for 
> changes to Dwarf 2 by the end of this year and release a version
> of the revised standard for public review early in 2001.
> 
> My experience is the same as Stan's.  Old formats don't disappear,
> and they certainly don't disappear because someone says that they
> should.  Plan for a long End-Of-Life status.

Then, as i said, i'm really going to need some help doing this.
--Dan


  parent reply	other threads:[~2000-10-11 12:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-10 17:38 Daniel Berlin
     [not found] ` <dberlin@redhat.com>
2000-10-10 18:19   ` Kevin Buettner
2000-10-10 19:42     ` Daniel Berlin
2000-10-10 23:54 ` Eli Zaretskii
     [not found] ` <20001010211904.49719@cse.cygnus.com>
     [not found]   ` <m3bswsds9s.fsf@dan2.cygnus.com>
2000-10-11  9:53     ` DJ Delorie
2000-10-11 12:51       ` Daniel Berlin
     [not found]     ` <20001011130611.11730@cse.cygnus.com>
2000-10-11 12:55       ` Daniel Berlin
     [not found] ` <39E4AEE2.2213F615@apple.com>
     [not found]   ` <39E4B09A.D096436F@eagercon.com>
2000-10-11 12:55     ` Daniel Berlin [this message]
2000-10-11 13:00       ` Michael Snyder

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=m3y9zv6tku.fsf@dan2.cygnus.com \
    --to=dberlin@redhat.com \
    --cc=eager@eagercon.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=shebs@apple.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