From: Jim Blandy <jimb@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mec.gnu@mindspring.com (Michael Elizabeth Chastain),
gdb@sources.redhat.com
Subject: Re: Delay the branch for E500 native support
Date: Tue, 06 Jul 2004 17:22:00 -0000 [thread overview]
Message-ID: <vt2d6396oic.fsf@zenia.home> (raw)
In-Reply-To: <2914-Sun04Jul2004001640+0300-eliz@gnu.org>
For what it's worth, I actually like feature-based scheduling, too.
It's inconsistent of me to suggest a delay.
I think my real motivation was just frustration: I've put, what, 45
patches in on this thing so far, and I really wanted to just get it
done.
I don't see any compelling reason to delay the branch. I'll get
everything onto the trunk, and we can see what people think.
next prev parent reply other threads:[~2004-07-06 17:22 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
2004-07-06 17:22 ` Jim Blandy [this message]
-- 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=vt2d6396oic.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=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