Autoconf

View Git repositories

Autoconf hosts its code at git://git.sv.gnu.org/autoconf.git.

You can learn more at the project's web page.

Launchpad imports the master branch and you can create branches from it.

You can browse the source code for the development focus branch or get a copy of the branch using the command:
bzr branch lp://staging/autoconf

There are download files available for Autoconf.

See all merge proposals.

Autoconf has 1 active branch owned by 1 team. There were 0 commits in the last month.

Bazaar branches

Name Status Last Modified Last Commit
lp://staging/autoconf
Series: main 		1 Development 2020-02-26 15:27:38 UTC
6547. Fix `make syntax-check'. There are t...

Author: Zack Weinberg
Revision Date: 2020-02-26 15:27:38 UTC

Fix `make syntax-check'.

There are two errors caught by make syntax-check currently.

First, the recent make update-copyright
(d78a7dd95fed24e417dfb4d08124a9ce7c1f7d1e) missed autoconf.texi, I
think because there are a bunch of .texi files in doc/ whose copyright
years should *not* be updated (e.g. standards.texi, fdl.texi) and the
exclusion pattern is too broad. I can't actually *find* the exclusion
pattern in the twisty maze of .mk files, all alike, so I just manually
updated autoconf.texi.

Second, it objects to an edit to an old section of NEWS. This is
because of d3dcd5895d64f6c86275c9333e2760a867e540e7, which is a
legitimate change (replacing http:// with https:// in a URL) so the
correct action is to change old_NEWS_hash to match.

 * doc/autoconf.texi: Update copyright year.
 * cfg.mk (old_NEWS_hash): Update to acknowledge commit
 d3dcd5895d64f6c86275c9333e2760a867e540e7.
1 → 1 of 1 result First • Previous • Next • Last
You can't create new branches for Autoconf.