On Tuesday 15 November 2011, Bruno Haible wrote:
Eric Blake wrote:
... on an unstable Debian using pcc
(Portable C Compiler, version 1.1.0~DEVEL+20110422-1
...
Warnings like this, and the error in test-float.c, mean that all other
packages using the same gnulib modules will have the
Okay to push?
* top/maint.mk (tight-scope.mk): Make sure to prefix file
reference with $(srcdir) so that the file is found correctly even
when running `make syntax-check' in a VPATH build.
Signed-off-by: Gary V. Vaughan g...@gnu.org
---
ChangeLog|7 +++
top/maint.mk |2 +-
2
Gary V. Vaughan wrote:
I think 'Copyright-paper-required: No' is still the best compromise here for
the reasons stated earlier in the thread.
Okay to push?
The FSF require that all non-trivial patches to its projects be
accompanied by appropriate paperwork, or that any patches that are
Hi Jim,
On 15 Nov 2011, at 18:14, Jim Meyering wrote:
Gary V. Vaughan wrote:
I think 'Copyright-paper-required: No' is still the best compromise here for
the reasons stated earlier in the thread.
Okay to push?
The FSF require that all non-trivial patches to its projects be
accompanied
Gary V. Vaughan wrote:
Hi Jim,
On 15 Nov 2011, at 18:14, Jim Meyering wrote:
Gary V. Vaughan wrote:
I think 'Copyright-paper-required: No' is still the best compromise here for
...
This is setting FSF policy,
Well, the policy is already set very clearly...
From
Hi Jim,
On 15 Nov 2011, at 19:02, Jim Meyering wrote:
Gary V. Vaughan wrote:
On 15 Nov 2011, at 18:14, Jim Meyering wrote:
Gary V. Vaughan wrote:
I think 'Copyright-paper-required: No' is still the best compromise here
for
...
This is setting FSF policy,
Well, the policy is already set
Gary V. Vaughan wrote:
Hi Jim,
On 15 Nov 2011, at 19:02, Jim Meyering wrote:
Gary V. Vaughan wrote:
On 15 Nov 2011, at 18:14, Jim Meyering wrote:
Gary V. Vaughan wrote:
I think 'Copyright-paper-required: No' is still the best compromise here
for
...
This is setting FSF policy,
Well,
Gary V. Vaughan wrote:
Okay to push?
* top/maint.mk (tight-scope.mk): Make sure to prefix file
reference with $(srcdir) so that the file is found correctly even
when running `make syntax-check' in a VPATH build.
...
tight-scope.mk: $(ME)
@rm -f $@ $@-t
- @perl -ne '/^#
Hi Jim,
On 15 Nov 2011, at 20:14, Jim Meyering wrote:
Gary V. Vaughan wrote:
Okay to push?
* top/maint.mk (tight-scope.mk): Make sure to prefix file
reference with $(srcdir) so that the file is found correctly even
when running `make syntax-check' in a VPATH build.
...
tight-scope.mk:
Hi Jim,
On 15 Nov 2011, at 20:10, Jim Meyering wrote:
Gary V. Vaughan wrote:
On 15 Nov 2011, at 19:02, Jim Meyering wrote:
Propose a patch to maintain.texi.
I don't want to get into a debate over the merits of generated
ChangeLogs with RMS, which I already know he doesn't like.
I don't
Hi All,
I was playing with some gnulib stuff tonight and noticed that if I
import only openat, I get errors when later running autoreconf:
configure.ac:17: warning: gl_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK is m4_require'd
but not m4_defun'd
m4/openat.m4:11: gl_FUNC_OPENAT is expanded from...
Hi Bruno,
I sent this to Jim last night as he's listed as the owner of gnulib on
savanah, but he suggested I send this to you (and bug-gnulib).
A while back I wrote a 'how to integrate gnulib'[1] tutorial that was
aimed at the OpenCSW maintainer community. We package software for
Solaris so
Hi,
Ben Walton wrote:
I was playing with some gnulib stuff tonight and noticed that if I
import only openat, I get errors when later running autoreconf:
configure.ac:17: warning: gl_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK is
m4_require'd but not m4_defun'd
m4/openat.m4:11: gl_FUNC_OPENAT is
Hi Ben,
Ben Walton wrote:
I sent this to Jim last night as he's listed as the owner of gnulib on
savanah, but he suggested I send this to you (and bug-gnulib).
Yes, things like this are suitable for public discussion.
A while back I wrote a 'how to integrate gnulib'[1] tutorial that was
14 matches
Mail list logo
