On Wed, Mar 17, 2010 at 02:43:38PM -0400, Christopher Faylor wrote:
>Right. And, as far as I can see, there is no mechanism within gzip to
>set the time to something special if stdin is not a regular file. It
>always seems to use the time that it gets from fstat(). On linux that
>apparently is t
On Wed, Mar 17, 2010 at 07:24:54PM +0100, Corinna Vinschen wrote:
>On Mar 17 19:15, Denis Excoffier wrote:
>>
>> On Wed, Mar 17, 2010 at 12:56:12PM +0100, Corinna Vinschen wrote:
>> >>
>> >> What impact? I don't think there is any standard which requires
>> a non
>> >> filesystem based stream to
On Mar 17 19:15, Denis Excoffier wrote:
>
> On Wed, Mar 17, 2010 at 12:56:12PM +0100, Corinna Vinschen wrote:
> >>
> >> What impact? I don't think there is any standard which requires
> a non
> >> filesystem based stream to have a current timestamp and a tool
> relying
> >> on that might be broke
On Wed, Mar 17, 2010 at 12:56:12PM +0100, Corinna Vinschen wrote:
>>
>> What impact? I don't think there is any standard which requires a
non
>> filesystem based stream to have a current timestamp and a tool
relying
>> on that might be broken. All our streams which are not backed by a
>> f
On Mar 16 18:24, Denis Excoffier wrote:
>
> Hello,
>
> Under Cygwin 1.7.1-1, i have created the small program (see below),
> to print the modification time of the standard input. In the case where
> the stdin is a pipe (or the terminal), i expect the result to be more
> or less the current time.
Hello,
Under Cygwin 1.7.1-1, i have created the small program (see below),
to print the modification time of the standard input. In the case where
the stdin is a pipe (or the terminal), i expect the result to be more
or less the current time. But the time printed in this case is
invariably the m
6 matches
Mail list logo
