From: Daniel Berlin <dberlin@dberlin.org>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: dwarf2expr.[ch]
Date: Mon, 08 Jul 2002 20:49:00 -0000 [thread overview]
Message-ID: <C2550BDA-92EE-11D6-867A-000393575BCC@dberlin.org> (raw)
In-Reply-To: <3D2A555C.9060500@ges.redhat.com>
On Monday, July 8, 2002, at 11:15 PM, Andrew Cagney wrote:
> Daniel,
>
> Just a reminder. As a GNU developer, you're expected to submit
> patches that meet the GNU coding standard. This is important as it
> saves on significiant run-around time spent by both yourself and the
> reviewer.
>
I'll just ignore this sentence, rather than point out just how absurd
this statement is when it comes to GDB development.
If you feel the need to remind me, I'm pretty sure you don't need to
copy gdb-patches and Jim. Especially since this seems to be a personal
message addressed to me.
Not that I mind, but i'm pretty sure Jim doesn't care, and it's
debatable whether anyone else does.
> I guess you ment, work-in-progress.
>
No, I diffed the wrong version.
It's a moot issue anyway, as I said, since it's just two new files that
are really part of another patch I need to resubmit with revisions
anyway.
the RFA was added by my mailer as the default subject prefix for new
messages gdb-patches and i didn't notice.
> enjoy,
> Andrew
>
>
next prev parent reply other threads:[~2002-07-09 3:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 16:48 Daniel Berlin
2002-07-08 20:20 ` Andrew Cagney
2002-07-08 20:49 ` Daniel Berlin [this message]
2002-07-08 21:12 ` Andrew Cagney
2002-07-09 15:21 ` Jim Blandy
2002-07-10 9:05 ` Andrew Cagney
2002-07-09 15:10 ` Jim Blandy
2002-07-09 16:00 ` Daniel Berlin
2002-07-10 11:18 ` Daniel Berlin
2002-07-10 12:48 ` Jim Blandy
2002-07-10 13:27 ` Daniel Berlin
2002-07-10 16:15 ` Jim Blandy
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=C2550BDA-92EE-11D6-867A-000393575BCC@dberlin.org \
--to=dberlin@dberlin.org \
--cc=ac131313@ges.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