From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: mec@shout.net
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] gdb.texinfo: new release tarball commands
Date: Sat, 11 Jan 2003 10:10:00 -0000 [thread overview]
Message-ID: <9003-Sat11Jan2003120644+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <200301102254.h0AMslR30036@duracef.shout.net> (message from Michael Elizabeth Chastain on Fri, 10 Jan 2003 16:54:47 -0600)
> Date: Fri, 10 Jan 2003 16:54:47 -0600
> From: Michael Elizabeth Chastain <mec@shout.net>
>
> Committed, with Eli Z's change of a period to a colon.
>
> Michael C
>
> 2003-01-09 Michael Chastain <mec@shout.net>
>
> * gdbint.texinfo (Configuring @value{GDBN} for Release): Delete.
> (Create a Release): Add new instructions for new @file{src-release}.
> Document existing instructions for @file{Makefile.in} as
> being for @value{GDBN} 5.3.1 or earlier.
It's not necessary to use @-commands in the ChangeLog entries. In
fact, it might be confusing.
Btw, if "Configuring @value{GDBN} for Release" is the node name, it
should be avoided: using @-commands in node names confuses TeX and
might cause warnings from makeinfo. But since this node was deleted,
I'm writing this just so we remember this in the future.
Thanks.
next prev parent reply other threads:[~2003-01-11 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 22:54 Michael Elizabeth Chastain
2003-01-11 10:10 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-10 21:28 Michael Elizabeth Chastain
2003-01-10 20:44 Michael Elizabeth Chastain
2003-01-10 20:34 Michael Elizabeth Chastain
2003-01-10 20:38 ` Andrew Cagney
2003-01-10 20:55 ` 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=9003-Sat11Jan2003120644+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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