I've fixed a few robustness problems in git's git-cvsserver. Once
savannah is running a version of git with that change (the patch is
already upstream, and will be in git-1.5.3), I'll feel better about
switching gnulib's upstream repo to git, and letting old-timers (:-)
use git's cvsserver
There are currently differences between maintain.texi and gpl-3.0.texi
about what the copyright header for each file distributed in an FSF-owned
GPLv3+ package should look like.
$ diff -u gpl maintain
--- gpl 2007-07-18 06:56:27.43750 -0600
+++ maintain2007-07-18 06:56:11.65625 -0600
Bruce Korb [EMAIL PROTECTED] ha escrit:
Would it make sense to simply provide the .po fragments
Actually, that's what we are doing now. The gnulib textual domain is
registered at TP and I update gnulib.pot file there from time to
time. Moreover, quite a few translations for it are already
Sergey Poznyakoff wrote:
The gnulib textual domain is
registered at TP and I update gnulib.pot file there from time to time.
Your updates have apparently not been registered:
http://translationproject.org/POT-files/gnulib-1.0.pot
is still from 2005-09-30.
Can you write to coordinator at
Jim Meyering [EMAIL PROTECTED] writes:
I've tested the following versions of git:
1.5.3.rc1.27.ga5e40
1.5.2.4
1.4.4.4
Very strange. I'm using Debian stable git (1.4.4.4).
E.g., from a git-cloned coreutils work area,
git-rm -n doc/.gitignore should exit successfully.
Does that
Hi,
In the hello-2.3 tarball the gnulib/lib/Makefile.am references
build-aux/link-warning.h, but this file is not included in the tarball!
This should fix it:
2007-07-18 Bruno Haible [EMAIL PROTECTED]
* gnulib-tool (func_get_automake_snippet): Synthesize also an
EXTRA_DIST
Paul Eggert [EMAIL PROTECTED] writes:
The rest of the v3 patch is
kinda large and is still being debugged.
An update on this. Part of the debugging is that we are awaiting some
policy clarifications from the FSF on the LGPLv2.1 - LPGLv3 upgrade.
Of course we support the move to v3 and intend
Eric Blake wrote:
Since the use of gnulib has the tendency to introduce translatable strings
into a project, should there be a way for gnulib-tool to mark which files
need to be added to POTFILES.in? Perhaps a new entry in each module
description that calls out any files with translatable
