From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: GDB Discussion <gdb@sources.redhat.com>
Subject: Re: 5.1 README
Date: Mon, 23 Jul 2001 09:38:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010723193604.20613K-100000@is> (raw)
In-Reply-To: <3B572CA1.6050203@cygnus.com>
On Thu, 19 Jul 2001, Andrew Cagney wrote:
> Several things I've noticed:
>
> o it recommends a separate build tree
> yet gives the same build tree example
> first
IIRC, this was discussed in the past, and we decided to leave it as it is
now. I don't see anything wrong with the current structure: after all,
for a typical user, keeping the source directory pristine is not very
important. Those who care will read the recommendation and act upon it.
> o it doesn't mention building PDF
This can be easily added. Should I do that?
P.S. Somebody should make sure the PDF version indeed can be built with
the popular version(s) of PDFTeX, before we advertise that.
next prev parent reply other threads:[~2001-07-23 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 10:25 Andrew Cagney
2001-07-08 1:19 ` Eli Zaretskii
2001-07-19 11:53 ` Andrew Cagney
2001-07-23 9:38 ` Eli Zaretskii [this message]
2001-07-23 13:56 ` Andrew Cagney
2001-07-25 8:01 ` Eli Zaretskii
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=Pine.SUN.3.91.1010723193604.20613K-100000@is \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=gdb@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