On the Windows platform, Microsoft documents the rename function
as refusing to replace existing destination files. This is
allowed by C89 (and C99) but it is not POSIX-compliant, and it
can be quite surprising to programs that want to atomically
replace files.
Here is the second version of the g
pretty much reached the end of that particular tedious limitation.
Not even remotely the case.
My request is, please stick to 7-bit ASCII whenever it is all feasible.
Names in ChangeLogs and the like are one thing, but randomly
throwing in UTF-8 (or any other encoding) into email (or source)
Hello,
Juergen Weber wrote:
> ERROR CCN3205 ./fpurge.c:119 "Please port gnulib fpurge.c to your
> platform! Look at the definitions of fflush, setvbuf and ungetc on your
> system, then report this to bug-gnulib."
>
> So, I am doing this ;-)
> The required definitions are linked from here:
> htt
Hi,
I tried to build bash-4.0 on IBM's z/OS 1.9.
It configures and builds up to fpurge:
ac99 -c -I. -I../.. -I../.. -I../../lib -I../../include -I.
-I../../lib/intl -I./bash-4.0/lib/intl -DHAVE_CONFIG_H -DSHELL
-I./bash-4.0/include fpurge.c
ERROR CCN3205 ./fpurge.c:119 "Please port gnuli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 4/7/2009 6:32 AM:
>> If you use Bruno's git-merge-changelog program, and attach a
>> .gitattributes notation to your changelog that you do so, then ChangeLog
>> diffs have a high probability of applying correctly,
>
> Tha
Eric Blake wrote:
> According to Jim Meyering on 4/7/2009 2:56 AM:
>> - use ChangeLog-style "* full-relative-name/to-each-affected-file
>> (func,rule,etc.): description..." in the log, because that is what
>> goes into the ChangeLog for gnulib. In coreutils, the log is the
>> primary sour
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 4/7/2009 2:56 AM:
> - use ChangeLog-style "* full-relative-name/to-each-affected-file
> (func,rule,etc.): description..." in the log, because that is what
> goes into the ChangeLog for gnulib. In coreutils, the log i
FYI, just pushed:
>From d29d6c11acd73086ac7ffabb9a451faa1d4984f9 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Tue, 7 Apr 2009 10:38:35 +0200
Subject: [PATCH] useless-if-before-free: show how to remove braced useless
free, too
* build-aux/useless-if-before-free: still only in a comment, tho
Reuben Thomas wrote:
...
> Which means I have to configure Emacs specially for writing certain
> files. It's a pain that in a system invented in the last ten years
> (git) UTF-8 is still a second-class citizen.
There's nothing wrong with git's UTF-8 support.
Reuben Thomas wrote:
> On Tue, 7 Apr 2009, Jim Meyering wrote:
>> Didn't you notice how it was harder to read your UTF8-encoded Subject
>> line in what I quoted?
>
> Yes, but that's because you pasted an encoded mail header into your reply.
No, I did not.
You attached the patch as type text/xdiff,
On Tue, 7 Apr 2009, Jim Meyering wrote:
Didn't you notice how it was harder to read your UTF8-encoded Subject
line in what I quoted?
Yes, but that's because you pasted an encoded mail header into your reply. I
normally only read mail headers in an MUA where they are displayed properly.
Are y
Reuben Thomas wrote:
> On Tue, 7 Apr 2009, Jim Meyering wrote:
>> - your summary/subject was needlessly utf8-encoded.
>> That makes it harder to read.
>
> For the sake of one apostrophe. It's a pity, I made Emacs do smart
> quotes in text mode, and now it looks like I need an exception. What'
On Tue, 7 Apr 2009, Jim Meyering wrote:
- your summary/subject was needlessly utf8-encoded.
That makes it harder to read.
For the sake of one apostrophe. It's a pity, I made Emacs do smart quotes in
text mode, and now it looks like I need an exception. What's the problem
with UTF-8 in
Reuben Thomas wrote:
> On Tue, 7 Apr 2009, Jim Meyering wrote:
>> Ok. Post "git format-patch ..." output and I'll push it,
>> unless someone objects in the mean time.
>
> Attached. Let me know if I did something wrong.
>
> (Copyright assignment: I'm assuming that since I didn't write any of
> this
On Tue, 7 Apr 2009, Jim Meyering wrote:
Ok. Post "git format-patch ..." output and I'll push it,
unless someone objects in the mean time.
Attached. Let me know if I did something wrong.
(Copyright assignment: I'm assuming that since I didn't write any of this,
but just made trivial changes,
15 matches
Mail list logo
