[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 20 clean-up csets on "next"
From: |
Jim Meyering |
Subject: |
Re: 20 clean-up csets on "next" |
Date: |
Mon, 30 Nov 2009 17:05:34 +0100 |
Jim Meyering wrote:
> I've just pushed 20 c-sets to next, here:
>
> http://git.savannah.gnu.org/gitweb/?p=grep.git;a=shortlog;h=refs/heads/next
>
> Overall summary: use more bits from gnulib and enable some of
> its syntax-checks (several more to go, see cfg.mk for the list).
>
> Object now if you see anything you don't like.
> Here's the summary:
>
> maint: list gnulib modules one per line
> maint: generate ChangeLog from git logs
> build: update gnulib submodule to latest
> build: get more lib/* files from gnulib, adjust savedir
> build: adapt to the newer exclude API we now get from gnulib
> build: adapt to the newer closeout module from gnulib
> build: add several build- and release-related gnulib modules
> build: use git-version-gen for inter-release version strings
> build: require automake-1.11, enable silent-rules, parallel tests, xz
> maint: disable the many failing syntax-checks
> maint: enable immutable_NEWS check
> maint: enable "file system" check
> maint: use gnulib's progname module; enable set_program_name check
> maint: enable require_config_h checks
> maint: enable unmarked_diagnostics check
> maint: enable trailing_blank check
> maint: enable makefile @...@ check
> maint: remove now-generated file: po/Makefile.in.in
> maint: enable makefile_path_separator check
> maint: enable two checks
>
> Tomorrow I'll pull everything onto master and remove next.
Nobody replied, so I've pushed those.
Note that the 2nd change makes it so there is no longer an explicitly
version-controlled ChangeLog file. Now, it is generated automatically
from the git commit log messages, so please be sure to write your
git commit log messages in the usual git+ChangeLog form:
(described in http://git.sv.gnu.org/cgit/coreutils.git/plain/HACKING)
The existing ChangeLog file was renamed to ChangeLog-2009,
and all new entries will be automatically included in the
ChangeLog file that is inserted into the tarball at "make dist" time.