From: Gerald Pfeifer <gerald@pfeifer.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
Alexandre Oliva <aoliva@redhat.com>,
Paolo Bonzini <paolo.bonzini@lu.unisi.ch>,
DJ Delorie <dj@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] codingconventions.html: autotools update
Date: Sun, 09 Sep 2007 22:32:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0709092351580.11229@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20070809201921.GA17798@ins.uni-bonn.de>
On Thu, 9 Aug 2007, Ralf Wildenhues wrote:
> please consider this patch to update the coding conventions web page.
> FYI, I do not have commit privs.
I was hoping one of our configury master would jump at this patch. ;-)
Alexandre, DJ, Paolo, would you mind having a look? If this is fine,
just let us know and I'll commit this on behalf of Ralf. Also, if you
request some changes, I'll be happy to make those and then commit an
update version.
Thanks,
Gerald
> 2007-08-09 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
>
> * htdocs/codingconventions.html: Update libtool file list.
> configure.in is now configure.ac.
>
> Index: htdocs/codingconventions.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v
> retrieving revision 1.51
> diff -u -r1.51 codingconventions.html
> --- htdocs/codingconventions.html 27 Jul 2007 04:50:47 -0000 1.51
> +++ htdocs/codingconventions.html 9 Aug 2007 19:52:14 -0000
> @@ -446,20 +446,22 @@
> meaningful and unique. Don't install the patch, install the whole
> file.</li>
>
> -<li>ltconfig, ltmain.sh, libtool.m4, ltcf-c.sh, ltcf-cxx.sh,
> +<li>ltmain.sh, libtool.m4, ltoptions.m4, ltsugar.m4, ltversion.m4,
> +lt~obsolete.m4, and formerly also ltconfig, ltcf-c.sh, ltcf-cxx.sh,
> ltcf-gcj.sh: The master copy of these files is the CVS repository of
> <a href="http://www.gnu.org/software/libtool/libtool.html">GNU
> libtool</a>. Patches should be posted to <a
> href="mailto:libtool-patches@gnu.org">libtool-patches@gnu.org</a>.
> Only after the change makes it to the libtool CVS tree should the new
> files be installed in the GCC source tree. ltconfig and ltmain.sh are
> -generated files from ltconfig.in and ltmain.in, respectively, so, when
> +generated files from ltconfig.in and ltmain.in, respectively, and with
> +libtool 2.1, the latter is generated from ltmain.m4sh, so, when
> you post the patch, make sure you're patching the source file, not the
> generated one. When you update these generated files in the GCC
> repository, make sure they report the same timestamp and version number,
> and note this version number in the ChangeLog.</li>
>
> -<li>Top-level configure.in, configure, Makefile.in, config-ml.in,
> +<li>Top-level configure.ac, configure, Makefile.in, config-ml.in,
> config.if and most other top-level shell-scripts: Please try to keep
> these files in sync with the corresponding files in the src repository
> at sourceware.org. Some people hope to eventually merge these
>
--
Gerald (Jerry) Pfeifer gerald@pfeifer.com http://www.pfeifer.com/gerald/
next prev parent reply other threads:[~2007-09-09 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 20:19 Ralf Wildenhues
2007-09-09 22:32 ` Gerald Pfeifer [this message]
2007-09-10 7:31 ` Paolo Bonzini
2007-09-10 19:06 ` Gerald Pfeifer
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=Pine.LNX.4.64.0709092351580.11229@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=paolo.bonzini@lu.unisi.ch \
/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).