From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: joseph@codesourcery.com, qpan@mvista.com, gdb@sources.redhat.com
Subject: Re: GDB 6.5 release process created
Date: Sat, 20 May 2006 00:18:00 -0000 [thread overview]
Message-ID: <20060519220733.GB16297@nevyn.them.org> (raw)
In-Reply-To: <200605192113.k4JLDYdH001365@elgar.sibelius.xs4all.nl>
On Fri, May 19, 2006 at 11:13:34PM +0200, Mark Kettenis wrote:
> > Date: Fri, 19 May 2006 10:25:24 +0000 (UTC)
> > From: "Joseph S. Myers" <joseph@codesourcery.com>
> >
> > On Thu, 18 May 2006, Daniel Jacobowitz wrote:
> >
> > > On Thu, May 18, 2006 at 10:29:44AM -0700, Qunying Pan wrote:
> > > > Hello:
> > > >
> > > > I noticed the gdb/configure file in this prerelease was generated by
> > > > autoconf 2.59d instead of autoconf 2.59. Should we fix it before release or
> > > > we are going to go with autoconf 2.59d?
> > >
> > > Do you think it makes a major difference? I hope it won't.
> >
> > It changes the default infodir and mandir (to follow a more recent version
> > of the GNU Coding Standards), so if different subdirectories use different
> > versions then different subdirectories may install documentation in
> > different places.
>
> Then I think we should stick to 2.59, until the next official autoconf
> release is out.
Yes, I agree. I didn't notice the problem even when I tested
packaging, because the new defaults (/usr/share/info and
/usr/share/doc) are what I've been configuring GDB to use for ages.
The current version is my fault; Debian/unstable upgraded to 2.59d.
Could someone else please regenerate it for me? At some point I'll
have to get a local installation of it together, but not tonight.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-05-19 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060516213808.6F8981B4BC@hermes.mvista.com>
2006-05-18 21:49 ` Qunying Pan
2006-05-19 3:27 ` Daniel Jacobowitz
2006-05-19 12:48 ` Joseph S. Myers
2006-05-19 17:50 ` Qunying Pan
2006-05-19 22:07 ` Mark Kettenis
2006-05-20 0:18 ` Daniel Jacobowitz [this message]
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=20060519220733.GB16297@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=joseph@codesourcery.com \
--cc=mark.kettenis@xs4all.nl \
--cc=qpan@mvista.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