On Wed, May 05, 2010 at 04:35:49PM +0100, Richard W.M. Jones wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x77ae77fe in __strncpy_sse2 (s1=,
> s2=, n=) at ./strncpy.c:83
> 83 *++s1 = '\0';
> (gdb) bt
> #0 0x77ae77fe in __strncpy_sse2 (s1=,
> s2=, n
Hi Richard,
> Program received signal SIGSEGV, Segmentation fault.
> 0x77ae77fe in __strncpy_sse2 (s1=,
> s2=, n=) at ./strncpy.c:83
> 83 *++s1 = '\0';
> (gdb) bt
> #0 0x77ae77fe in __strncpy_sse2 (s1=,
> s2=, n=) at ./strncpy.c:83
> #1 0x77b071d2 in __getl
Eric Blake writes:
> We've started using the _GL_ prefix, rather than GL_, because the
> package OpenGL uses the GL_ prefix
> s/one one/one/ ...
> Do you also want to check that it actually increments? And wouldn't
> __LINE__ be a slightly better fallback than 0?...
All good points, thanks;
Yes, from the FSF side of things, having the FSF own the copyright is
handy for upgrading licenses;
Probably everyone here knows, but for the archives: FSF holding
copyright is about more than being handy for license changes. It's
about defending the program's copyright in court. This i
On 05/05/2010 01:55 PM, Paul Eggert wrote:
> To fix the problem you mentioned with verify.h, I installed the
> following patch into gnulib. It uses the new __COUNTER__ macro of GCC
> (4.3 and later), which is designed for this problem. So this should fix
> the warnings for GCC 4.3 and later. Old
Hi Peter,
> There is a pread module, but no pwrite. This is a mostly mechanical
> patch, copying the pread bits and s/read/write/ and copying pwrite.c
> from glibc.
Thanks. I committed this in your name.
You certainly hate paperwork as much as I do. I don't see a copyright
assignment for you and
> http://sources.redhat.com/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=d84acf388ed8b3f162dda0512139095bfc268beb
>
> commit d84acf388ed8b3f162dda0512139095bfc268beb
> Author: Andreas Schwab
> Date: Wed May 5 09:59:25 2010 -0700
>
> Fix lookup of collation sequence value during regexp matching
Eric Blake writes:
>* This implementation exploits the fact that GCC does not warn about
> the last declaration mentioned above. If a future version of GCC
> introduces a warning for this, the problem could be worked around
> by using code specialized to GCC, e.g.,:
>
>
$ EXEEXT='' srcdir='.' LOCALE_FR='fr_FR' LOCALE_FR_UTF8='fr_FR.UTF-8'
LOCALE_JA='ja_JP' LOCALE_ZH_CN='zh_CN.GB18030' LOCALE_FR_UTF8='fr_FR.UTF-8'
LOCALE_FR='fr_FR' LOCALE_FR_UTF8='fr_FR.UTF-8' LOCALE_JA='ja_JP'
LOCALE_ZH_CN='zh_CN.GB18030' gdb --args ./test-getlogin_r
GNU gdb (GDB) Fedora (7.0-
On 05/04/2010 09:53 AM, Peter Seebach wrote:
> 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 fo
On 05/04/2010 05:53 PM, Peter Seebach wrote:
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 re
Peter Seebach wrote:
> 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 ca
Hello Peter,
* Peter Seebach wrote on Tue, May 04, 2010 at 05:53:56PM CEST:
> 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 i
Hi,
There is a pread module, but no pwrite. This is a mostly mechanical
patch, copying the pread bits and s/read/write/ and copying pwrite.c
from glibc.
2010-05-05 Peter O'Gorman
New module pwrite
* doc/posix-functions/pread.texi: Mention gnulib module.
* doc/posix-fun
In message <201005042150.o44lolls015...@f7.net>, Karl Berry writes:
>Aside from that: the FSF will also accept a copyright disclaimer,
>putting changes in the public domain. So if that's your preference (as
>I think I saw in another message), it is fine.
Ahh, that would work nicely.
My proposal
Hi Peter,
if the FSF needs a copyright assignment, does that not imply that I
no longer get to choose the copyright?
As the author, your desire/recommendation would carry a lot of weight :).
If you want it released under LGPLv2+, I can't imagine there being a
problem with that.
Aside fro
16 matches
Mail list logo
