Re: [PATCH 0/2] Bump copyright

2012-12-31 Thread Paul Eggert
On 12/31/2012 04:46 PM, Eric Blake wrote: > It's still 2012 in my time zone, but 2013 UTC, so I feel safe pushing > this now. Hah! For GNU tar, I temporarily switched to Tokyo time before pushing, so I beat you by a few hours. http://git.savannah.gnu.org/cgit/tar.git/commit/?id=cd7bdd4076ca15457

[PATCH 0/2] Bump copyright

2012-12-31 Thread Eric Blake
It's still 2012 in my time zone, but 2013 UTC, so I feel safe pushing this now. Eric Blake (2): version-etc: bump copyright year reported in --version maint: update all copyright year number ranges ChangeLog| 7 ++- MODULES.html.sh

[PATCH 1/2] version-etc: bump copyright year reported in --version

2012-12-31 Thread Eric Blake
Compare to commit fc9846f from last year. * lib/version-etc.c (COPYRIGHT_YEAR): Update to 2013. Signed-off-by: Eric Blake --- ChangeLog | 7 ++- lib/version-etc.c | 4 ++-- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index df7999e..70c8269 10

[PATCH 2/2] maint: update all copyright year number ranges

2012-12-31 Thread Eric Blake
Run "make update-copyright". Compare to commit 1602f0a from last year. Signed-off-by: Eric Blake --- MODULES.html.sh | 2 +- ... users.txt| 2 +- 3624 files changed, 3625 insertions(+), 3625 deletions(-) diff --gi

[PATCH] sigprocmask-tests: skip test if pid is unexpectedly large

2012-12-31 Thread Eric Blake
At least mingw64 has 8-byte pid_t but only 4-byte long. Silent truncation to int in printing a pid value with %d risks killing the wrong process. But rather than try to futz with determining the maximum pid_t, it is simpler to just cap things by realizing that this test is already skipped on ming

[PATCH] git-version-gen: avoid test -z portability glitch

2012-12-31 Thread Eric Blake
Autoconf warns that there are some broken shells where 'test -z "$x"' gives 0 exit status if $x is ')'. Since some of our strings come from command-line arguments, and since git-version-gen is run on end-user machines where sh might be broken, we should be robust to abuse. Some of the instances r

Re: [PATCH v5 2/2] git-version-gen: add --fallback option to use if git is not present

2012-12-31 Thread Eric Blake
On 12/28/2012 04:45 PM, Peter Rosin wrote: > When building in a git checkout, but from a system lacking git, it > is useful to fall back to the version determined when the git > checkout was last used from a system sporting git. > > * build-aux/git-version-gen: Add support for the new option --fal

Re: [PATCH v4 2/2] git-version-gen: add --fallback option to use if git is not present

2012-12-31 Thread Eric Blake
On 12/28/2012 03:13 PM, Peter Rosin wrote: > When building in a git checkout, but from a system lacking git, it > is useful to fall back to the version determined when the git > checkout was last used from a system sporting git. > > * build-aux/git-version-gen: Add support for the new option --fal

Re: git-version-gen w/o git

2012-12-31 Thread Eric Blake
On 12/28/2012 04:45 PM, Peter Rosin wrote: >>> Sure thing, I also rebased them while at it... >> >> ...but forgot the script-version. v4 coming up. >> >> Sorry for the noise. > > But sent the wrong patch anyway and also omitted the subject. > > *blush* > > v5 coming up. Ugg, I saw v4 and pushed

Re: [PATCH v4 1/2] maint.mk: handle missing git with more grace

2012-12-31 Thread Eric Blake
On 12/28/2012 03:13 PM, Peter Rosin wrote: > * top/maint.mk (no-submodule-changes, public-submodule-commit): Quietly > proceed if git is not present. > > Copyright-paperwork-exempt: yes > Signed-off-by: Peter Rosin > --- > top/maint.mk |6 -- > 1 files changed, 4 insertions(+), 2 deletio

[PATCH] dup2: work around cygwin bug

2012-12-31 Thread Eric Blake
Detected by './gnulib-tool --test dup2 cloexec'. Reported upstream: http://cygwin.com/ml/cygwin/2012-12/msg00377.html and fixed already: http://cygwin.com/ml/cygwin-cvs/2012-q4/msg00202.html but as we want to work with older cygwin, we'll have to carry this in gnulib for a while. * m4/dup2.m4 (gl_

Re: inline problems on RHEL 5.8

2012-12-31 Thread Eric Blake
On 12/31/2012 09:57 AM, Eric Blake wrote: > How do I go about debugging and fixing these errors? I suspect they are > more fallout from Paul's efforts to revamp how 'inline' works; these > were reproduced by temporarily bumping m4 to the latest gnulib.git and > compiling on a RHEL 5.8 machine (ker

inline problems on RHEL 5.8

2012-12-31 Thread Eric Blake
How do I go about debugging and fixing these errors? I suspect they are more fallout from Paul's efforts to revamp how 'inline' works; these were reproduced by temporarily bumping m4 to the latest gnulib.git and compiling on a RHEL 5.8 machine (kernel 2.6.18, glibc 2.5, gcc 4.6.4): gcc -std=gnu99