From: Tom Tromey <tromey@redhat.com>
To: Stefano Lattarini <stefano.lattarini@gmail.com>
Cc: ams@gnu.org, iant@google.com, gcc@gcc.gnu.org,
11034@debbugs.gnu.org, gdb@sourceware.org,
automake@gnu.org, binutils@sourceware.org,
joseph@codesourcery.com
Subject: Re: bug#11034: Binutils, GDB, GCC and Automake's 'cygnus' option
Date: Mon, 02 Apr 2012 15:16:00 -0000 [thread overview]
Message-ID: <87ty12i2pd.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F79BFDB.1070904@gmail.com> (Stefano Lattarini's message of "Mon, 02 Apr 2012 17:03:55 +0200")
>>>>> "Stefano" == Stefano Lattarini <stefano.lattarini@gmail.com> writes:
Stefano> True, and that was even stated in the manual; the whole point
Stefano> of ditching support for cygnus trees is that by now those two
Stefano> big users are basically not making any real use of the 'cygnus'
Stefano> option anymore. To quote my previous report:
Stefano> ./bfd/doc/Makefile.in:AUTOMAKE_OPTIONS = 1.9 cygnus
Stefano> ./bfd/doc/Makefile.in:# cygnus option.
Stefano> ./bfd/doc/Makefile.am:AUTOMAKE_OPTIONS = 1.9 cygnus
Stefano> ./bfd/doc/Makefile.am:# cygnus option.
But this is a reason not to remove it; or at least to restore the
previous handling of info files.
I don't care about the cygnus option per se. It was always a grab bag
of hacks. The issue is removing a feature that an important user relies
on. So far the suggested replacements haven't seemed that good to me.
Tom
next prev parent reply other threads:[~2012-04-02 15:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 10:05 Stefano Lattarini
2012-03-28 11:25 ` Joseph S. Myers
2012-03-28 12:20 ` Stefano Lattarini
2012-03-28 12:29 ` Joseph S. Myers
2012-03-28 13:02 ` Stefano Lattarini
2012-03-28 23:43 ` Ian Lance Taylor
2012-03-31 8:30 ` bug#11034: " Stefano Lattarini
2012-03-31 9:08 ` Alfred M. Szmidt
2012-03-31 10:14 ` Stefano Lattarini
2012-04-04 13:17 ` Joseph S. Myers
2012-04-05 12:04 ` Stefano Lattarini
[not found] ` <4F76D8F2.8050804__46768.5595191599$1333188914$gmane$org@gmail.com>
2012-04-02 14:25 ` Tom Tromey
2012-04-02 15:04 ` Stefano Lattarini
2012-04-02 15:16 ` Tom Tromey [this message]
2012-04-02 15:30 ` Stefano Lattarini
[not found] ` <4F79C5F2.2020807__46832.8654104427$1333380662$gmane$org@gmail.com>
2012-04-02 19:36 ` Tom Tromey
2012-04-02 19:51 ` Stefano Lattarini
[not found] ` <4F7A0341.9050305__49963.8538728051$1333396325$gmane$org@gmail.com>
2012-04-02 20:19 ` Tom Tromey
2012-04-02 20:50 ` Stefano Lattarini
2012-04-02 21:10 ` Ian Lance Taylor
2012-04-03 20:04 ` Stefano Lattarini
2012-04-03 20:05 ` Stefano Lattarini
2012-04-03 20:29 ` Stefano Lattarini
2012-04-03 20:40 ` Tom Tromey
2012-04-04 7:43 ` Stefano Lattarini
2012-04-03 21:08 ` Ian Lance Taylor
2012-04-03 21:40 ` Pedro Alves
2012-04-03 23:53 ` Miles Bader
2012-04-04 7:47 ` Stefano Lattarini
2012-04-04 9:03 ` Pedro Alves
2012-04-03 8:23 ` Joern Rennecke
2012-03-31 11:39 ` Stefano Lattarini
2012-03-31 16:42 ` bug#11034: " Stefano Lattarini
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=87ty12i2pd.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=11034@debbugs.gnu.org \
--cc=ams@gnu.org \
--cc=automake@gnu.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=iant@google.com \
--cc=joseph@codesourcery.com \
--cc=stefano.lattarini@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).