Mark McGranaghan
518a807773
Rebuild
2015-02-24 19:13:33 -08:00
Steve Krulewitz
684013f5e0
Fix a few small typos.
2015-02-22 21:52:25 -08:00
Mark McGranaghan
0e5edb053d
Just elide this
2014-04-15 18:17:55 -07:00
Mark McGranaghan
915697101b
More consistent use of layout vs format
2014-04-15 18:14:23 -07:00
Mark McGranaghan
a8ee83af78
Emphasize time constants
...
In most cases users will format and parse times using the constants
provided in package time. Show these first before getting into custom
example-based formats.
2014-04-15 18:09:28 -07:00
Mark McGranaghan
3c5392df99
Rebuild
2014-01-10 06:34:13 -08:00
Mark McGranaghan
b2d1ba5cd8
Tweak time formatting wording
...
Use non-teletype to indicate that it's the logical
values that need to be exact, not the specific text
which will vary by format.
2014-01-10 06:33:03 -08:00
Will Leinweber
c214c51286
Be explicit about time parsing
...
How did anyone think this was a good idea?
2014-01-07 14:13:59 -08:00
pattichen
6dcdfc2d36
Correct time parse result
2013-10-26 10:18:37 -07:00
Mark McGranaghan
afdf0cc2b4
add trailing newlines
2013-10-06 08:50:23 -07:00
Mark McGranaghan
e77dcdddd4
missing some generated files
2013-09-11 09:01:11 -07:00
Mark McGranaghan
a6ec750f4a
fix kitchen times, show an example of constants
2012-11-02 09:35:39 -07:00
Mark McGranaghan
0bfce8f576
call it kitchen
2012-11-02 06:51:29 -07:00
Mark McGranaghan
7f1e1860f2
use named formats
2012-11-01 22:59:53 -07:00
Mark McGranaghan
5110cee76a
publish time-formatting-parsing
2012-11-01 15:26:20 -07:00
