From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: RFA: document GDB's overlay support
Date: Sun, 02 Dec 2001 21:57:00 -0000 [thread overview]
Message-ID: <3C0B145E.1000900@cygnus.com> (raw)
In-Reply-To: <np667rdg3b.fsf@zwingli.cygnus.com>
> That would be simpler.
>
> I guess I wanted to provide instructions for putting your build system
> back in a "working normal" state: you type "cvs update", "configure",
> and "make", and things just work, without needing to remember to copy
> over certain files.
>
> But obviously, the instructions should mention the simpler
> alternative, for those less forgetful than me.
It needs to work for the snapshot process - PDF, PS and HTML. It
definitly appears to do that!
v-nice description,
Andrew
next prev parent reply other threads:[~2001-12-03 5:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 15:06 Jim Blandy
2001-11-25 1:01 ` Eli Zaretskii
2001-11-25 8:33 ` Jim Blandy
2001-11-25 10:57 ` Eli Zaretskii
2001-11-30 22:53 ` Eli Zaretskii
2001-11-30 14:53 ` Jim Blandy
2001-12-02 21:57 ` Andrew Cagney [this message]
2001-11-30 13:58 ` Eli Zaretskii
2001-11-30 12:57 ` 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=3C0B145E.1000900@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@cygnus.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