From: Andrew Cagney <ac131313@cygnus.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Andrew Cagney <cagney@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: ARM simulator maintainer
Date: Fri, 11 Jan 2002 11:06:00 -0000 [thread overview]
Message-ID: <3C3F37A4.6070603@cygnus.com> (raw)
In-Reply-To: <20020111133107.D29520@redhat.com>
> Hi -
>
> cagney wrote:
>
>> [...]
>> Hidden intent? I would like an active GDB/SIM developer co-ordinating
>> sim. You must admit you're not exactly active so I'm stepping forward.
>
>
> I didn't realize that my performance of this relatively ceremonial and
> unofficial role was measured thusly.
That is a very interesting.
I'm expecting the person cordinating the sim directory to be activly
encouraging and contributing to that code's development: setting its
direction, anticipating problems with GDB, adding new features, and so
on. You appear to be describing it as something that looks good at the
bottom of a resume :-(
It could be a misunderstanding of the expected role or perhaphs that the
expectations of the role are changing.
Andrew
next prev parent reply other threads:[~2002-01-11 19:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 15:00 RFC: ARM simulator coredump Fred Fish
2002-01-09 15:31 ` Andrew Cagney
2002-01-10 3:28 ` Nick Clifton
2002-01-10 7:15 ` Andrew Cagney
2002-01-10 8:13 ` Nick Clifton
2002-01-10 3:29 ` ARM simulator maintainer Nick Clifton
2002-01-10 7:19 ` Andrew Cagney
2002-01-10 8:11 ` Nick Clifton
2002-01-10 8:31 ` Frank Ch. Eigler
2002-01-10 16:29 ` Andrew Cagney
2002-01-10 17:22 ` Frank Ch. Eigler
2002-01-10 17:34 ` Andrew Cagney
2002-01-10 17:53 ` Frank Ch. Eigler
2002-01-10 18:08 ` Andrew Cagney
2002-01-11 10:31 ` Frank Ch. Eigler
2002-01-11 11:06 ` Andrew Cagney [this message]
2002-01-10 7:33 ` RFC: ARM simulator coredump Richard Earnshaw
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=3C3F37A4.6070603@cygnus.com \
--to=ac131313@cygnus.com \
--cc=cagney@redhat.com \
--cc=fche@redhat.com \
--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