From: "Eli Zaretskii" <eliz@gnu.org>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: gdb@sources.redhat.com
Subject: Re: Delay the branch for E500 native support
Date: Sat, 03 Jul 2004 21:16:00 -0000 [thread overview]
Message-ID: <2914-Sun04Jul2004001640+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040703114543.71C864B104@berman.michael-chastain.com> (mec.gnu@mindspring.com)
> Date: Sat, 3 Jul 2004 07:45:43 -0400 (EDT)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
>
> The disadvantage of feature-based scheduling is that right after
> each feature comes one more feature.
I didn't suggest feature-based schedule, I just said that we shouldn't
be treating time-based schedule as too sacred.
Also, we are not talking about adding a new feature, we are talking
about finishing a feature that's already in the codebase.
next prev parent reply other threads:[~2004-07-03 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 11:45 Michael Elizabeth Chastain
2004-07-03 21:16 ` Eli Zaretskii [this message]
2004-07-06 17:22 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2004-07-02 22:27 Jim Blandy
2004-07-02 22:40 ` Daniel Jacobowitz
2004-07-03 9:28 ` Eli Zaretskii
2004-07-04 6:14 ` Daniel Jacobowitz
2004-07-04 19:20 ` Eli Zaretskii
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=2914-Sun04Jul2004001640+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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