On Sun, Feb 14, 2010 at 03:02:14PM +0100, Jim Meyering wrote:
> Colin Watson wrote:
> > I looked at converting man-db to use Gnulib's hash implementation rather
> > than its own. One obstacle seems to be that there is one place where
> > man-db cares about the difference between a key not being in
Peter Simons wrote:
> yes, that change would solve my problem. Thank you very much.
Ok. Pushed.
Hi Jim,
yes, that change would solve my problem. Thank you very much.
Take care,
Peter
Peter Simons wrote:
> I'm using gnulib for the autoconf-archive project. To upload a new release,
> I have to use the following invocation of gnupload:
>
> ./build-aux/gnupload --to dl.sv.nongnu.org:/releases/autoconf-archive/
> file1 file2 ...
>
> Now, it doesn't seem possible to configure gnul
Hi,
I'm using gnulib for the autoconf-archive project. To upload a new release,
I have to use the following invocation of gnupload:
./build-aux/gnupload --to dl.sv.nongnu.org:/releases/autoconf-archive/ file1
file2 ...
Now, it doesn't seem possible to configure gnulib's emit_upload_commands
t
Colin Watson wrote:
> I looked at converting man-db to use Gnulib's hash implementation rather
> than its own. One obstacle seems to be that there is one place where
> man-db cares about the difference between a key not being in the hash at
> all, and a key being in the hash but with a NULL value
I spotted three more unnecessary #include directives in coreutils'
remove.c, so here's as syntax-check rule that would have detected one
of them:
>From e1b83155bc5e95f4165b806850e4117426479a68 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Sun, 14 Feb 2010 11:22:29 +0100
Subject: [PATCH] maint
