Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Zaretskii Eli <ezaretski@elta.co.il>
To: Elena Zannoni <ezannoni@redhat.com>,
	Raoul Gough <RaoulGough@yahoo.co.uk>
Cc: gdb-patches@sources.redhat.com
Subject: RE: [RFA] DLLs without debugging symbols (repost)
Date: Thu, 20 Feb 2003 20:11:00 -0000	[thread overview]
Message-ID: <4D19136444628A40840EFE8C5AE04147017A46@ELTIMAIL1.elta.co.il> (raw)


This message was scanned for viruses and other malicious code by PrivaWall.


This mail was sent from ELTA SYS LTD.


> From: Elena Zannoni [mailto:ezannoni@redhat.com] 
> Sent: Thursday, February 20, 2003 4:00 AM
> 
> The texinfo stuff should be approved by Eli. Mybe post it as a
> separate [RFA/doco] message, it will be more likely to be noticed.

Sorry, I did miss the original message.

The doco patch is approved, but please put "kernel32.dll" inside @file.

Also, please use "---" (three dashes in a row) instead of just "-" when
you want an em-dash in the manual.

Symbol names such as ``KERNEL32!CreateFileA'' should be in @code (and
without the quotes).

Instead of "(see @ref{Symbols})", please use "(@pxref{Symbols})".

Finally, I suggest some @cindex entry about symbol names in non-debug
DLLs somewhere in the text.  Users might look for this information in
the index.

Thanks!
 


This message is processed by the PrivaWall Email Security Server. 


             reply	other threads:[~2003-02-20 20:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 20:11 Zaretskii Eli [this message]
2003-02-23 17:46 ` Raoul Gough
2003-02-23 17:53   ` Christopher Faylor
2003-02-23 19:09     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2003-02-06 22:55 Raoul Gough
2003-02-06 23:36 ` Christopher Faylor
2003-02-11 21:46   ` Raoul Gough
2003-02-11 21:52     ` Elena Zannoni
2003-02-20  1:55 ` Elena Zannoni
2003-02-20  2:18 ` Elena Zannoni
2003-02-20  3:14   ` Christopher Faylor
2003-02-23 17:48     ` Raoul Gough

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=4D19136444628A40840EFE8C5AE04147017A46@ELTIMAIL1.elta.co.il \
    --to=ezaretski@elta.co.il \
    --cc=RaoulGough@yahoo.co.uk \
    --cc=ezannoni@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