Olivier Delhomme <[EMAIL PROTECTED]> wrote:
>
[25 lines of unnecessary context removed -- please trim context of
quoted messages]
> Thank you for replying so quickly,
> sorry for that mistake, i'm so confused. Here is the patch
> against today's cvs sources :
Thank you for the patch.
Have you
Dennis Smit <[EMAIL PROTECTED]> wrote:
> I would like to implement the following todo item:
>
> du and wc: add an option to make them read NUL-delimited
> file name arguments from a file.
>
> I there anything i should know i start, how would you prefer
> the option to be called?
You should file
On Sat, 8 Nov 2003, Bob Proulx wrote:
[rm and unexecutable directories]
>>the other way is to chmod every file before doing anything with
>>it.
>But the directory containing the file would need the chmod, not the
>file itself.
Sorry - I meant to say chmod every directory before doing anything
w
On Sat, 8 Nov 2003, Bob Proulx wrote:
% mkdir -p fred/jim
% chmod a-x fred/jim
% rm -rf fred
rm: cannot chdir from `fred' to `jim': Permission denied
>>>
>>>But by the action of your chmod you have specifically requested that
>>>you do not want those files removed!
>>
>>But by spec
Heya!, i will look into the papers!, have you already
received the -c --total patch for df ?
I will think about what kind of option i could use for that file
name list option for du and wc.
Also i have been looking in the vsclite test, however i will set up an
new machine to run the test so i won
Jim Meyering <[EMAIL PROTECTED]> writes:
> Maybe `--files-from', since GNU tar uses that, but those names
> aren't separated with NUL bytes.
>
> Other ideas?
tar uses --files-from=NAME (-T NAME) to read files from NAME, and a
separate option --null to say that the file names are NUL-terminated
r
Paul Eggert <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>> Maybe `--files-from', since GNU tar uses that, but those names
>> aren't separated with NUL bytes.
>>
>> Other ideas?
>
> tar uses --files-from=NAME (-T NAME) to read files from NAME, and a
> separate option --null
Le Sun, 09 Nov 2003 10:27:45 +0100, Jim Meyering disait :
> Thank you for the patch.
>
> Have you read the GNU Coding Standards document?
No, not yet, but this mistake will soon be patched :)
> Run `info standards' on a Linux system. There are
> some minor syntactic problems below. Most wou
Title: Failed tests in 'make check'
OS: Solaris 7 (Sun SPARC)
The attached file contains the pertinent excerpt of what was reported by 'make check' run as root.
--aslam
Aslam Karachiwala
Online Development, Insurance
Thomson Media (Sheshunoff Information Services)
One Alewife Center, Sui
I must admit that my preference goes to eggerts method because
it also allows newline terminated filenames within the file
which is human readable and editable.
We'll use --files-from, -T for the option i assume ? and when agreed upon
optionaly an --null flag.
_
10 matches
Mail list logo