From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Brian Youmans <3diff@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: new diff: gdb.texinfo
Date: Sun, 20 Jan 2002 09:33:00 -0000 [thread overview]
Message-ID: <3C4AFF7A.2030801@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020120134722.9986C@is>
> On Thu, 17 Jan 2002, Andrew Cagney wrote:
>
>
>> > Andrew, I don't know whether I should bother checking in these changes
>> > on the branch anymore, what with your intent to release v5.2 from the
>> > trunk. Please advise.
>
>>
>> The still need to go onto the 5.1 branch because these are fixing (C)
>> problems and I'm going to have to spin another 5.1.something with those
>> fixes included (sigh).
>
>
> Okay, I committed to the branch as well. But please check whether making
> a distribution from the branch works, including "make info", because
> something strange happened with fdl.texi on the branch, probably because
> CVS and myself don't get along very well ;-)
FYI, I try to remember to do this but ... I'm adding a checklist it to
the release process.
The best way to check the doco on the 5.1 branch:
http://sources.redhat.com/gdb/5.1/onlinedocs/
it is updated once every 24hrs.
Andrew
next prev parent reply other threads:[~2002-01-20 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 14:13 Brian Youmans
2002-01-16 23:38 ` Eli Zaretskii
2002-01-17 8:31 ` Andrew Cagney
2002-01-17 12:28 ` Eli Zaretskii
2002-01-20 3:49 ` Eli Zaretskii
2002-01-20 9:33 ` Andrew Cagney [this message]
2002-01-20 10:27 ` Eli Zaretskii
2002-01-17 2:59 ` Richard Earnshaw
2002-01-17 3:59 ` Eli Zaretskii
2002-01-17 7:21 ` Brian Youmans
2002-01-17 7:41 ` Richard Earnshaw
2002-01-20 3:48 ` 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=3C4AFF7A.2030801@cygnus.com \
--to=ac131313@cygnus.com \
--cc=3diff@gnu.org \
--cc=eliz@is.elta.co.il \
--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