From: "Qunying Pan" <qpan@mvista.com>
To: "'Joseph S. Myers'" <joseph@codesourcery.com>,
"'Daniel Jacobowitz'" <drow@false.org>
Cc: <gdb@sources.redhat.com>
Subject: RE: GDB 6.5 release process created
Date: Fri, 19 May 2006 17:50:00 -0000 [thread overview]
Message-ID: <20060519163021.ED0301B51C@hermes.mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605191023570.18955@digraph.polyomino.org.uk>
>> > 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.
Thanks for the replies. Doesn't make a major difference, but at least it
will generate a trunk of unrelated diff when a user regenerates configure
file using 2.59 if there is any update. It is a little annoying. It will be
great if we could remain consistent with the version, either 2.59 or 2.59d,
as it won't make much difference with the real result. Since 2.59 is more
widely used, probably it is better to go for?
Best Regards,
Qunying
next prev parent reply other threads:[~2006-05-19 16:30 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 [this message]
2006-05-19 22:07 ` Mark Kettenis
2006-05-20 0:18 ` Daniel Jacobowitz
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=20060519163021.ED0301B51C@hermes.mvista.com \
--to=qpan@mvista.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=joseph@codesourcery.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