From: "Eli Zaretskii" <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: jimb@redhat.com, gdb@sources.redhat.com
Subject: Re: Delay the branch for E500 native support
Date: Sat, 03 Jul 2004 09:28:00 -0000 [thread overview]
Message-ID: <7137-Sat03Jul2004122237+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040702224047.GA21295@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 2 Jul 2004 18:40:47 -0400)
> Date: Fri, 2 Jul 2004 18:40:47 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> I would really have liked for GDB 6.1 to contain inter-compilation-unit
> reference support too. If the timing doesn't work out, it doesn't work
> out - if the schedule holds there may even be another release this
> year.
The intercu example is not a good analogy, IMHO: it was a new feature
that was totally absent from the codebase.
Jim's situation is somewhat different: there's a half-baked port
already in the CVS. To me, it doesn't make sense to release a new
version with incomplete support for some platform, where work is under
way to make it complete in a week or so.
But then I never liked the ``release every N months no matter what''
policy, either. What's so sacred about having the release happen on
a certain date in July, anyway?
next prev parent reply other threads:[~2004-07-03 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 22:27 Jim Blandy
2004-07-02 22:40 ` Daniel Jacobowitz
2004-07-03 9:28 ` Eli Zaretskii [this message]
2004-07-04 6:14 ` Daniel Jacobowitz
2004-07-04 19:20 ` Eli Zaretskii
2004-07-03 11:45 Michael Elizabeth Chastain
2004-07-03 21:16 ` Eli Zaretskii
2004-07-06 17:22 ` Jim Blandy
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=7137-Sat03Jul2004122237+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.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