From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: dan@cgsoftware.com
Cc: jimb@zwingli.cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: Rewriting the type system
Date: Tue, 12 Jun 2001 10:01:00 -0000 [thread overview]
Message-ID: <7458-Tue12Jun2001195810+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <87k82hisn2.fsf@cgsoftware.com>
> From: Daniel Berlin <dan@cgsoftware.com>
> Date: 12 Jun 2001 12:12:49 -0400
>
> > In other words, the development procedures work.
> Maybe for your area of GDB.
> Not for mine.
> And apparently, not for some others.
It's possible that some maintainers are less responsive than others,
and that I had luck talking to one kind while you to the other. By
posting my experience I didn't mean to say that you made up this
stuff. I just wanted to put things into a proper perspective.
> Do you really think i'd complain if I was alone here?
I don't think it's wrong to complain about slow response. _How_ you
complain is important, however.
next prev parent reply other threads:[~2001-06-12 10:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-07 23:22 obvious set_cu_language patch Per Bothner
2001-06-07 23:50 ` Daniel Berlin
2001-06-08 11:01 ` Per Bothner
2001-06-08 14:04 ` Stan Shebs
2001-06-08 14:34 ` Daniel Berlin
2001-06-08 13:04 ` Andrew Cagney
[not found] ` <m2pucevgf6.fsf@kelso.bothner.com>
2001-06-08 13:51 ` Daniel Berlin
[not found] ` <8766e6eke4.fsf@creche.redhat.com>
2001-06-08 14:23 ` Per Bothner
[not found] ` <npelsq28sh.fsf_-_@zwingli.cygnus.com>
2001-06-11 11:43 ` Rewriting the type system Daniel Berlin
2001-06-11 16:58 ` Stan Shebs
2001-06-12 1:44 ` Eli Zaretskii
2001-06-12 9:12 ` Daniel Berlin
2001-06-12 10:01 ` Eli Zaretskii [this message]
2001-06-12 10:16 ` Jim Blandy
2001-06-12 10:44 ` Daniel Berlin
2001-06-12 14:02 ` Stan Shebs
2001-06-13 1:45 ` Eli Zaretskii
2001-06-12 11:08 ` Daniel Berlin
2001-06-12 14:03 ` Andrew Cagney
2001-06-12 21:37 ` Daniel Berlin
2001-06-25 14:13 ` obvious set_cu_language patch Elena Zannoni
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=7458-Tue12Jun2001195810+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=dan@cgsoftware.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zwingli.cygnus.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