This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: gdb-5.0/gdb/doc/Makefile.in patch -- is this patch really correct?
- To: shebs at apple dot com
- Subject: Re: gdb-5.0/gdb/doc/Makefile.in patch -- is this patch really correct?
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Sat, 1 Jul 2000 03:07:55 -0400 (EDT)
- CC: gdb-patches at sourceware dot cygnus dot com, ac131313 at cygnus dot com
- References: <200006231835.OAA07083@fwr.landmark.com> <200006250818.EAA07995@indy.delorie.com> <20000630010635.A14862@cygnus.com> <200006300846.EAA14373@indy.delorie.com> <20000630101845.A5618@cygnus.com> <200006301646.MAA14807@indy.delorie.com> <395CEAFF.C954873D@apple.com>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Fri, 30 Jun 2000 11:46:24 -0700
> From: Stan Shebs <shebs@apple.com>
>
> Should the info file be in CVS? Well, the manual doesn't change so
> routinely that info file updates would be time-consuming, but by the
> same token very few people are going to feel the need; if they even
> look at the info pages, they will most likely look at the installed
> ones. So I think we'd need to see some sort of compelling problem
> that would be solved by changing the current practice.
What worries me, as I wrote in this thread, is how can we possibly
make sure that any given change is not going to break either a
maintainer's setup or the end-user's setup, if these two have
different files in different directories?