From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Improve i386 prologue analyzer
Date: Thu, 12 Aug 2004 19:00:00 -0000 [thread overview]
Message-ID: <2914-Thu12Aug2004215629+0300-eliz@gnu.org> (raw)
In-Reply-To: <411B65D0.1040900@gnu.org> (message from Andrew Cagney on Thu, 12 Aug 2004 08:42:56 -0400)
> Date: Thu, 12 Aug 2004 08:42:56 -0400
> From: Andrew Cagney <cagney@gnu.org>
>
> Please, please, articulate the `pain on our part' that we're apparently
> all suffering. I'm the release manager, if anyone is is going to
> experience pain, it's going to be me.
Yes, and I don't think we should dismiss your pain (==loss of time) so
easily.
> > It's also the pain of our users
> > who will need to install two versions within 4 weeks.
>
> This update is for _MIPS_ users only. The next update is for _i386_
> users only.
What about people (or sysadmins) who need both, e.g. because they
actually make a good use of the multi-arch features and debug several
different CPUs from the same system?
Anyway, those are not the important issues here.
> > And I still don't understand what is the rush to release the MIPS
> > patch without waiting for another week or two and then releasing the
> > i386 patch as well.
>
> If I were a MIPS user (hmm, I'm even the maintainer), I'd be pretty
> cheesed off that a fix to get `break main; run' working was being held
> back due the inistance that it be bundled with an unrelated i386 fix.
Sorry, Andrew, this is just reiterating what I already said I didn't
understand: if we care so much for the MIPS, why did you refuse to
wait for it to be fixed in 6.2? And if 6.2 could hit the street with
MIPS broken, why cannot it stay broken for a week or two more, instead
of letting the i386 remain broken longer?
I keep asking this same question for about eternity, and you keep not
answering it, for some reason that is beyond me. It's embarrassing.
If there is some logic that would show why these two decisions do not
contradict each other, please explain that logic. You don't need my
agreement to go ahead, but I think I deserve to at least know your
reasoning, even if I disagree.
next prev parent reply other threads:[~2004-08-12 19:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-01 21:58 Mark Kettenis
2004-08-02 4:04 ` Eli Zaretskii
2004-08-02 21:19 ` Andrew Cagney
2004-08-03 3:55 ` Eli Zaretskii
2004-08-06 19:33 ` Mark Kettenis
2004-08-06 20:29 ` Andrew Cagney
2004-08-07 15:37 ` Eli Zaretskii
2004-08-07 16:20 ` Andrew Cagney
2004-08-07 17:11 ` Eli Zaretskii
2004-08-07 17:38 ` Andrew Cagney
2004-08-07 18:30 ` Joel Brobecker
2004-08-07 18:52 ` Andrew Cagney
2004-08-07 22:41 ` Michael Chastain
2004-08-08 3:57 ` Eli Zaretskii
2004-08-08 10:24 ` Michael Chastain
2004-08-08 11:08 ` Mark Kettenis
2004-08-08 14:08 ` Andrew Cagney
2004-08-08 15:04 ` Mark Kettenis
2004-08-08 19:32 ` Eli Zaretskii
2004-08-09 13:59 ` Andrew Cagney
2004-08-09 15:07 ` Mark Kettenis
2004-08-09 16:46 ` Michael Chastain
2004-08-09 19:09 ` Eli Zaretskii
2004-08-11 0:02 ` Andrew Cagney
2004-08-11 3:53 ` Eli Zaretskii
2004-08-11 17:13 ` Andrew Cagney
2004-08-11 17:55 ` Eli Zaretskii
2004-08-12 12:43 ` Andrew Cagney
2004-08-12 19:00 ` Eli Zaretskii [this message]
2004-08-12 21:41 ` Andrew Cagney
2004-08-08 19:29 ` Eli Zaretskii
2004-08-08 19:28 ` Eli Zaretskii
2004-08-07 15:31 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2003-08-18 9:42 Michael Elizabeth Chastain
2003-08-18 17:17 ` Mark Kettenis
2003-08-17 23:34 Michael Elizabeth Chastain
2003-08-17 23:16 Mark Kettenis
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-Thu12Aug2004215629+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.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