linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Neil Brown <neilb@suse.de>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
	Al Viro <viro@ftp.linux.org.uk>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linuxram@us.ibm.com
Subject: Re: [OT] Re: [PATCH 3/18] allow callers of seq_open do allocation themselves
Date: Mon, 7 Nov 2005 19:45:27 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0511071937130.3247@g5.osdl.org> (raw)
In-Reply-To: <17264.6769.472245.973213@cse.unsw.edu.au>



On Tue, 8 Nov 2005, Neil Brown wrote:
> On Monday November 7, rdunlap@xenotime.net wrote:
> > 
> > What format is that date in, please?
> 
>  %s %z
> 
> (as date(1) understands it).

Yes. It happens to be one of the formats git understands, and is also 
the least ambiguous. 

> Or was this a rhetorical question, meaning to say "Who in their right
> mind would used that sort of date format on a public mailing list?" :-)

Yeah, it's really only machine-readable. In this case git-readable, 
although git will accept dates in almost any format.

It happens to be the format internally used by git, since it's easy to 
parse and you can't get it wrong.

It may be a mistake to expose it outside in that format, though. The git 
"format patch as email" script will just use the internal date format, 
which is nice from a "you can't get it wrong" angle, but arguably not very 
human-friendly.

Not being able to get it wrong by converting it to a human-readable format 
and then converting it back is a pretty big advantage, though (it's damn 
easy to screw up summer-time and timezone when converting to/from UTC: 
the "%s %z" format doesn't leave any confusion: the seconds is always 
since the epoch in UTC, and the %z is purely informational to tell in 
which timezone the change was made).

			Linus

  parent reply	other threads:[~2005-11-08  3:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08  2:01 [PATCH 3/18] allow callers of seq_open do allocation themselves Al Viro
2005-11-08  3:03 ` [OT] " Randy.Dunlap
2005-11-08  3:24   ` Neil Brown
2005-11-08  3:12     ` Randy.Dunlap
2005-11-08  3:30     ` Al Viro
2005-11-08  3:48       ` Linus Torvalds
2005-11-08  3:45     ` Linus Torvalds [this message]
2005-11-08 20:33 ` Jonathan Corbet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0511071937130.3247@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@us.ibm.com \
    --cc=neilb@suse.de \
    --cc=rdunlap@xenotime.net \
    --cc=viro@ftp.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).