From: Eli Zaretskii <eliz@elta.co.il>
To: Andrew Cagney <cagney@gnu.org>
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [patch] Fix chng-syms.exp for remote stubs
Date: Sun, 29 Feb 2004 06:50:00 -0000 [thread overview]
Message-ID: <ud67yml90.fsf@elta.co.il> (raw)
In-Reply-To: <404157D8.7020704@gnu.org> (message from Andrew Cagney on Sat, 28 Feb 2004 22:09:12 -0500)
> Date: Sat, 28 Feb 2004 22:09:12 -0500
> From: Andrew Cagney <cagney@gnu.org>
>
> Daniel, what the f- are you doing? I'm half way through cutting a
> branch, the last thing I need is you being a fly-by nighter checking in
> random stuff.
Please let's refrain from such language here, no matter what. A
volunteer such as Daniel working on a Free Software project doesn't
deserve this, ever.
May I suggest counting to 10 before pressing the SEND button? I find
this practice very useful in cases like this.
prev parent reply other threads:[~2004-02-29 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 17:48 Daniel Jacobowitz
2004-02-29 2:56 ` Daniel Jacobowitz
2004-02-29 3:09 ` Andrew Cagney
2004-02-29 6:50 ` Eli Zaretskii [this message]
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=ud67yml90.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=cagney@gnu.org \
--cc=drow@false.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