Improve the man pages of --date=STRING for 'date' and 'touch'.

In an attempt to improve the 'date' and 'touch' man pages here is a proposal for a concise description of --date=STRING. Bob git fetch --no-tags git://git.proulx.com/coreutils date-string:date-string Improve the man pages of --date=STRING for 'date' and 'touch'. * man/date.x: Add a compact de

Re: coreutils: 'touch --date=STRING' docs don't tell what format STRING is.

A. Costa wrote: > repopen 363011 ! How do you suggest that we resolve this issue? > M. Stone wrote: > > The info documentation does indicate that the "Date input formats" > > can be used for -d. The difficulty in finding that documentation > > continues to be the broken install-info program. If y

Re: Bug#401939: closed by Michael Stone <[EMAIL PROTECTED]> (Re: od dumps byte-swapped words instead of bytes)

Please maintain the CC to both the bug number and the mailing list when responding. Thanks. David Lawyer wrote: > This bug still exists. Did you see my previous response to your bug report? It appears that you did not for some reason. You can read the exchange in the bug database here: http

[EMAIL PROTECTED]: coreutils problem]

I can readily duplicate this bug report on a 2.6.24-rc7 kernel by running `ls -l /proc/sys/fs/inotify` Kernel bug? libselinux bug? Documentation bug? I suppose coreutils should check that the returned context is non-NULL. It looks like the debian 5.97-5.3 selinux patch (derived from redhat)

Re: PDT timezone bug in GNU coreutils "date" v6.9

On Jan 28, 2008 1:23 AM, Bob Proulx <[EMAIL PROTECTED]> wrote: > What should be done when the timezone is ambiguous? That's a tiny minority of cases, and a case which many people will not think to check. Therefore I think the most helpful thing a tool can do is fail with an explanatory message.

Re: mv symlink-to-dir/, debian bug feed

On Jan 28, 2008 12:45 AM, Bob Proulx <[EMAIL PROTECTED]> wrote: > For all distros perhaps being more aggressive at forwarding downstream > bugs to the upstream mailing list would be a good thing. I know that > I have not been doing that as much as I should. I could not agree more. I often find

Re: [PATCH] Use strdup in dd to avoid changing argv elements

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Andreas Schwab on 1/28/2008 7:21 AM: | I think you are mixing up something here. This statement is only | related to the fact that a call to exec* must not modify any of the argv | and envp strings, despite the difficulty of expressing t

Re: [PATCH] Use strdup in dd to avoid changing argv elements

Jim Meyering <[EMAIL PROTECTED]> writes: > Eric Blake <[EMAIL PROTECTED]> wrote: > >> According to Jim Meyering on 1/28/2008 6:28 AM: >> | >> | Thanks for the suggestion, but that introduces a new way for >> | dd to fail: strdup returning NULL would often lead to a segfault. >> | Even if it were t

Re: [PATCH] Use strdup in dd to avoid changing argv elements

Eric Blake <[EMAIL PROTECTED]> writes: > http://www.opengroup.org/onlinepubs/009695399/functions/execl.html > "The statement about argv[] and envp[] being constants is included to make > explicit to future writers of language bindings that these objects are > completely constant. Due to a limitati

Re: [PATCH] Use strdup in dd to avoid changing argv elements

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 1/28/2008 6:28 AM: > | > | Thanks for the suggestion, but that introduces a new way for > | dd to fail: strdup returning NULL would often lead to a segfault. > | Even if it were to use xstrdup, to avoid that, I don't think it's >

Re: [PATCH] Use strdup in dd to avoid changing argv elements

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jim Meyering on 1/28/2008 6:28 AM: | | Thanks for the suggestion, but that introduces a new way for | dd to fail: strdup returning NULL would often lead to a segfault. | Even if it were to use xstrdup, to avoid that, I don't think it's |

Re: [PATCH] Use strdup in dd to avoid changing argv elements

Adam Goode <[EMAIL PROTECTED]> wrote: > Right now, dd uses strchr to do some parsing of argv. This messes up how > dd appears in ps. > > Here is a very simple solution to this problem. Yes, it does not free > memory. But does it matter? dd is just a standalone application. ... > diff --git a/src/dd

Re: rename("symlink-to-dir/", "name") behavior

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Geoff Clare on 1/28/2008 2:57 AM: |> |> My strict reading of the current wording in draft 4 does not permit Linux' |> behavior (even though it is more useful, in my opinion), since the |> trailing slash on B/ means that the old argument n

[PATCH] Use strdup in dd to avoid changing argv elements

Hi, Right now, dd uses strchr to do some parsing of argv. This messes up how dd appears in ps. Here is a very simple solution to this problem. Yes, it does not free memory. But does it matter? dd is just a standalone application. (Pointed out by Benjamin Gilbert.) Adam --- src/dd.c |2