From: "Raoul Gough" <RaoulGough@yahoo.co.uk>
To: gdb-patches@sources.redhat.com
Subject: Re: coffread.c extension for DLLs without debugging symbols
Date: Sat, 04 Jan 2003 16:21:00 -0000 [thread overview]
Message-ID: <av71ko$g21$1@main.gmane.org> (raw)
In-Reply-To: <2110-Sat04Jan2003130101+0200-eliz@is.elta.co.il>
"Eli Zaretskii" <eliz@is.elta.co.il> wrote in message
news:2110-Sat04Jan2003130101+0200-eliz@is.elta.co.il...
> > From: "Raoul Gough" <RaoulGough@yahoo.co.uk>
> > Date: Fri, 3 Jan 2003 19:39:31 -0000
> >
> > This is my *first* gdb patch submission,
> > so someone with more experience should probably take a good look
at
> > (e.g. is coffread.c the right place for this kind of code?).
>
> Lesson number 1: post the diffs as plain text, not uuencoded or
> otherwise encoded. Some people, such as myself, don't have time to
> open binary attachments, but do have time to read a patch that's in
> plain text.
OK, point taken. I was assuming that it was better to reduce some
bandwidth, given the size of the patch (circa 10kB). OK, you can all
laugh at me now for being so bandwidth-challenged that I still think
about that stuff :-)
>
> Also, please include "[RFA]" in the subject, so that we know you are
> seeking an approval for your patch.
What does RFA stand for? Seemed to me like it was used by people who
were actually capable of updating the CVS themselves and just wanted
confirmation.
>
> > Proposed ChangeLog entry, assuming the code is accepted:
> >
> > 2003-01-03 Raoul Gough <RaoulGough@yahoo.co.uk>
> >
> > * coffread.c: Support non-debug export symbols for win32 DLLs
>
> This should mention every function where changes are made,
preferably
> with a description of a change in each one of them.
Done! See my reply to Christopher Faylor on the patches mailing list.
>
> And thanks for working on this.
No problem - hope it's useful to some people.
Regards,
Raoul Gough.
next prev parent reply other threads:[~2003-01-04 16:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 19:41 Raoul Gough
2003-01-04 0:53 ` Michael Snyder
2003-01-04 4:43 ` Christopher Faylor
2003-01-04 16:31 ` Raoul Gough
2003-01-04 17:54 ` Eli Zaretskii
2003-01-04 20:51 ` Christopher Faylor
2003-01-05 14:44 ` Mark Kettenis
2003-01-05 17:18 ` Christopher Faylor
2003-01-05 17:40 ` Daniel Jacobowitz
2003-01-07 1:03 ` Raoul Gough
2003-01-07 1:12 ` Daniel Jacobowitz
2003-01-07 13:11 ` Raoul Gough
2003-01-07 16:46 ` Christopher Faylor
2003-01-07 2:28 ` Michael Snyder
2003-01-07 2:24 ` Michael Snyder
2003-01-04 11:03 ` Eli Zaretskii
2003-01-04 16:21 ` Raoul Gough [this message]
2003-01-06 17:10 ` Elena Zannoni
2003-01-06 17:41 ` Christopher Faylor
2003-01-07 0:46 ` Raoul Gough
2003-01-07 1:53 ` Elena Zannoni
2003-01-10 22:45 ` Raoul Gough
2003-01-07 1:00 ` Andrew Cagney
2003-01-10 22:37 ` Raoul Gough
2003-01-04 16:42 Michael Elizabeth Chastain
2003-01-05 15:40 ` Andrew Cagney
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='av71ko$g21$1@main.gmane.org' \
--to=raoulgough@yahoo.co.uk \
--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