Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Zaretskii Eli <ezaretski@elta.co.il>
To: Jelmer Vernooij <jelmer@nl.linux.org>,
	Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com, Andrew Cagney <ac131313@redhat.com>
Subject: RE: [PATCH] mi-symbol-*
Date: Wed, 19 Feb 2003 06:06:00 -0000	[thread overview]
Message-ID: <4D19136444628A40840EFE8C5AE04147017A2D@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: Jelmer Vernooij [mailto:jelmer@nl.linux.org] 
> Sent: Tuesday, February 18, 2003 8:45 PM
> 
> On Wed, Nov 06, 2002 at 08:56:23AM +0200, Eli Zaretskii wrote 
> about 'Re: [PATCH] mi-symbol-*':
> > The documentation patch is approved, but please take care 
> of these minor 
> > problems before it is committed:
> > 
> >  - Please break all lines inside @smallexample that are 
> longer than 64 
> >    characters, otherwise they will produce warnings from  TeX and
ugly 
> >    results in the printed manual.  (You can tell in a note that the 
> >    broken line is one long line.)
> > 
> >  - Why did you add so many empty lines?  IMHO, this produces >>
unpleasant 
> >    results, both in the on-line (Info and HTML) and printed formats.
> > 
> >  - Where you say "pattern", please add that the pattern is  a
regular 
> >    expression.
> All fixed; is the update ok?

Perhaps it is; but I didn't see the fixed patch.  Did I miss something?


This message is processed by the PrivaWall Email Security Server. 


             reply	other threads:[~2003-02-19  6:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19  6:06 Zaretskii Eli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-05 12:46 Jelmer Vernooij
2002-11-05 22:56 ` Eli Zaretskii
2003-02-01 22:08   ` Jelmer Vernooij
2003-02-11 17:08   ` Jelmer Vernooij
2003-02-18 18:45   ` Jelmer Vernooij
2002-11-07  9:04 ` Elena Zannoni
2003-04-28 20:23 ` Jelmer Vernooij
2002-11-02  9:35 Jelmer Vernooij

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=4D19136444628A40840EFE8C5AE04147017A2D@ELTIMAIL1.elta.co.il \
    --to=ezaretski@elta.co.il \
    --cc=ac131313@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jelmer@nl.linux.org \
    /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