Re: setproctitle()

2010-05-04 Thread Peter Seebach
In message <4be03f2d.7090...@redhat.com>, Eric Blake writes: >As original author, you get to choose the license that will be used >within gnulib. I see nothing wrong with you declaring that the >setproctitle module is LGPLv2+. Ahh, okay. That said, the more I look at this, the less sure I am tha

Re: setproctitle()

2010-05-04 Thread Peter Seebach
In message , "Alfred M. Szmidt" writes: >If the FSF is the copyright holder, then there is no (legal) need to >ask the original author about permission to relicense the work. It >might be a nice thing to do, but if the original author says no for >some reason, the FSF can still relicense the work;

Re: setproctitle()

2010-05-04 Thread Alfred M. Szmidt
>> Can you simply declare the copyright to be LGPLv2+? Many >> modules are already LGPLv2+ (see modules/*). > > I could if I were just releasing the code myself, but if the FSF > needs a copyright assignment, does that not imply that I no > longer get to choose the copyright?

Re: setproctitle()

2010-05-04 Thread Eric Blake
On 05/04/2010 09:21 AM, Peter Seebach wrote: > In message <87r5lr51hh@meyering.net>, Jim Meyering writes: >> Can you simply declare the copyright to be LGPLv2+? >> Many modules are already LGPLv2+ (see modules/*). > > I could if I were just releasing the code myself, but if the FSF needs > a c

Re: setproctitle()

2010-05-04 Thread Peter Seebach
In message <87r5lr51hh@meyering.net>, Jim Meyering writes: >Can you simply declare the copyright to be LGPLv2+? >Many modules are already LGPLv2+ (see modules/*). I could if I were just releasing the code myself, but if the FSF needs a copyright assignment, does that not imply that I no longer

[PATCH] docs: update cygwin progress

2010-05-04 Thread Eric Blake
* doc/posix-functions/wctob.texi (wctob): Cygwin 1.7.6 will fix this bug. * doc/glibc-functions/get_nprocs_conf.texi (get_nprocs_conf): Added in cygwin 1.7.2. * doc/glibc-functions/get_phys_pages.texi (get_phys_pages): Likewise. * doc/glibc-functions/get_avphys_pages.texi (get_avphys_pages): Likewi

Re: setproctitle()

2010-05-04 Thread Jim Meyering
Peter Seebach wrote: > In message <87hbmo5fzq@meyering.net>, Jim Meyering writes: >>Thanks for volunteering. Yes, this would be useful. >>There are many implementations floating around. > > There are indeed a ton. > >>Can you assign copyright to the FSF? > > I think I can. There is some ambi

Re: setproctitle()

2010-05-04 Thread Bruno Haible
Peter Seebach wrote: > Is there any interest in attempting to provide a moderately portable > setproctitle()? Yes, because it looks like a portable implementation will have to use different approaches on different platforms. [1] has the following: - use the function setproctitle. - use pstat(P

[PATCH] gendocs.sh: make its "-s FILE" option more useful

2010-05-04 Thread Jim Meyering
One more piece required. Without this, "gendocs.sh -s $(srcdir)/diff.texi" continued to try to use names like diffutils.info, while only "diff.info" was generated. >From cbbec352566be60d2ede1ee43f6bc911e547d8b0 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Tue, 4 May 2010 09:43:05 +0200 Subje

Re: setproctitle()

2010-05-04 Thread Peter Seebach
In message <87hbmo5fzq@meyering.net>, Jim Meyering writes: >Thanks for volunteering. Yes, this would be useful. >There are many implementations floating around. There are indeed a ton. >Can you assign copyright to the FSF? I think I can. There is some ambiguity about the IP agreement at $d