hello,
i'm happy that so much later someone cares about my bug-report.
Am 31.12.2018 um 05:13 schrieb Assaf Gordon:
> Hello,
>
> On 2018-07-23 9:54 a.m., kalle wrote:
>> in the documentation of ls the concept of the different times is not
>> explained sufficiently well
,
and I would also like to see language usage becoming easier (maybe in
the direction of 'simple english'), but I didn't do anything on the
latter yet.
Looking at my bug-reports on coreutils' bug-list
(https://debbugs.gnu.org/cgi/pkgreport.cgi?which=submitter=kalle%40projektwerkstatt.de)
, I see
THODs are":
-> for better readability, the above sentence should be started with a
new paragraph, since it is not related to information, whether the
option `-b' corresponds to some Emacs-variable or not...
greetings,
kalle
I already sent this mail on 19.05.2018, but since I got no response and
my bug-report then had be closed and I just unarchived and reopened it,
here again my message.
> Am 10.12.2017 um 01:23 schrieb Pádraig Brady:
>> On 16/11/17 03:36, kalle wrote:
>> here some mistakes/improv
Am 11.06.2018 um 01:38 schrieb Pádraig Brady:> On 19/05/18 00:54, kalle
wrote:
>> hello,
>> I have coreutils 8.26
>> and the option
>>
>> cp --attributes only FILE OTHERFILE
>>
>> correctly doesn't copy the content of FILE,
>> but the modificat
unarchive 31712
see "The valid METHODS are"
-> for better readability, the above sentence should be started with a
new paragraph, since it is not related to information, whether the
option `-b' corresponds to some Emacs-variable or not...
greetings,
kalle
hello,
in the documentation of ls the concept of the different times is not
explained sufficiently well (mtime, atime, ctime).
greetings,
kalle
it make sense in the spirit of UNIX philosophy to have only one
specialized command with the different capabilities included ??
greetings,
kalle
hello,
I have coreutils 8.26
and the option
cp --attributes only FILE OTHERFILE
correctly doesn't copy the content of FILE,
but the modification time of OTHERFILE is the actual date, whereas I
understood that it should be the same as in FILE.
kalle
Am 04.04.2018 um 00:10 schrieb Paul Eggert:
> On 04/03/2018 12:29 PM, kalle wrote:
>>
>> But what do you think of my teaching concept, to try to explain why a
>> `7' in `755' means =4+2+1=111=rwx="rwx for owner", which is assumed as
>> self-evident or intuiti
uot;are sometimes special" to
"have a special meaning for directories" ?
>
> I also merged Bug#31043 with Bug#29069 since they're the same topic.
The problem was, that when writing "Bug#29069" in the subject, nobody
responded to my patch proposal, which at the end was nearly to frustrating.
greetings,
kalle
hello,
below a patch proposal of mine.
kalle
>From b250dcdaba02083a0174d9157c655f0dbb586ef6 Mon Sep 17 00:00:00 2001
From: kalle <ka...@projektwerkstatt.de>
Date: Wed, 3 Jan 2018 20:56:07 +0100
Subject: [PATCH] changed presentation in 'File permissions' in 'numeric
modes'
I
le to give in the patches
myself. But for my last 2 mails sending in my patch proposals, no
response came...
here now for the 4th time again my patch proposal for chapter 27.3:
>From b250dcdaba02083a0174d9157c655f0dbb586ef6 Mon Sep 17 00:00:00 2001
From: kalle <ka...@projektwerkstatt.de&g
until now, no one responded to my patch proposal neither encorporated
it as I see.
why not?
kalle
Weitergeleitete Nachricht
Betreff: Fwd: Re: bug#29069: info coreutils file permissions:
improvements/bug-report
Datum: Wed, 31 Jan 2018 00:55:31 +0100
Von: kalle <
hello
I wonder why for the ls-command I don't find the following features, I
consider important:
- list the size of files. For directories, list the total size of the
tree beneath them
- for ls -R (recursive presentation) limit it to a certain depth
greetings,
kalle
I have a patch for chapter 27.3, coreutils texinfo-document.
greetings,
kalle
From b250dcdaba02083a0174d9157c655f0dbb586ef6 Mon Sep 17 00:00:00 2001
From: kalle <ka...@projektwerkstatt.de>
Date: Wed, 3 Jan 2018 20:56:07 +0100
Subject: [PATCH] changed presentation in 'File permi
Am 16.12.2017 um 22:14 schrieb Assaf Gordon:
> Hello,
>
> On 2017-12-16 01:52 PM, kalle wrote:
>> did you plan to respond my mail?
>
> Please remember GNU coreutils is maintained by volunteers.
> We aim for best effort in incorporating improvement suggest
On 09.11.2017 11:53, Bernhard Voelker wrote:
On 11/08/2017 11:54 AM, kalle wrote:
info chmod doesn't say, which users can apply it successfully. The same
for info chown.
Well, it does - indirectly:
https://www.gnu.org/software/coreutils/manual/html_node/chmod-invocation.html#chmod
hello,
- at the sentence "by default does not truncate": what does truncating a
file means? Could this be described better in the manual?
-part "on a busy system": why is this written here? Is this a usual
method to overwrite content?
thanks,
kalle
hello,
what I think is missing in info coreutils/page `dd' are better
explanations of[f the concept of a 'block' and what the
block-length/property blocked - unblocked means to a file.
greetings,
kalle
hould be
added ", if the user has write-permission in the containing directory."
-part "-i": shouldn't be written "When copying to a file" instead?
greetings,
kalle
s
> soon as possible -> more users, less mistakes..
No. Since it is not standard documentation I am a bit exhausted by
discussion about corrections in free software community in difficult
english just now. I would prefer to not correct this mistake now. What
about you?
greetings,
kalle
info chmod doesn't say, which users can apply it successfully. The same
for info chown.
Are the related man-pages also maintained by GNU coreutils? They also
have the same deficiencies...
greetings,
kalle
hi,
the parts concerning 27.3 (numeric modes) have been put into a different
e-mail by me.
>On 2017-10-30 02:38 PM, kalle wrote:
>> here some improvement proposals/bug report on info coreutils file
permissions:
>>
>> -in my opinion it would be good to explain the general
hello there,
this e-mail continues the discussion about improvement proposals about
info coreutils,section "File permissions". '>>' was me
(ka...@projektwerkstatt.de writing, '>' was assafgor...@gmail.com
This mail continues the specialized debate about `27.3 (numeric modes)'.
>> -27.3: is
is a GNU extension". Which
behavior is meant? And if it concerns the whole section 27.5, it should
be put right at the beginning.
greetings,
kalle
hmm. no one is responding anymore. No change in cat-Documentation then?
Am 25.07.2017 um 00:31 schrieb kalle:
>
>
> Am 30.05.2017 um 00:08 schrieb Pádraig Brady:
>> On 29/05/17 14:06, kalle wrote:
>>> hello,
>>> I think it is not obvious for everyon
hello,
I think it is not obvious for everyone how to deal with Standard Input in the
`cat'-command. I took some time to figure out, that Ctrl-d aborts it. and just
now I realized, that EOF the first time acts to terminate a so called "record"
(I got the term from "info coreutils 'tac'"), and
' etc will not generate segment fault.
Looking forward for a reply, regards,
Kalle Skott
[EMAIL PROTECTED]
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
I am listed in coreutils-5.0.90/THANKS as [EMAIL PROTECTED].
Please change the address to [EMAIL PROTECTED].
___
Bug-coreutils mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-coreutils
31 matches
Mail list logo
