| 1 |
On 5 September 2015 at 01:12, Aaron W. Swenson <titanofold@g.o> wrote: |
| 2 |
> Would you consider dropping the TZ offset? If the script were to translate |
| 3 |
> the DT to UTC, that'd remove some noise and shorten the line by 5. |
| 4 |
|
| 5 |
+1 |
| 6 |
|
| 7 |
> dev-java/antenna 2015-09-03 13:45:07Z monsieurp b4215f4 |
| 8 |
> |
| 9 |
> And I know what my offset is from UTC so I know the above example |
| 10 |
> happened at 11:45am my time, but having to do more math on the others |
| 11 |
> before figuring out my time is a little annoying. I can live with it, |
| 12 |
> but I'm lazy. |
| 13 |
|
| 14 |
I'm curious why the time part is even necessary, or at least, |
| 15 |
necessary at that accuracy. |
| 16 |
Day seems to be all that is necessary at most, and even then, you |
| 17 |
could reduce that down to a single number ( because its assumed to be |
| 18 |
from "now" to "a weekago" and the inference can be made, and maybe for |
| 19 |
convenience, use "days ago", or somethig. |
| 20 |
|
| 21 |
If you're needing the timestamps to try work out which commit |
| 22 |
something happened, the SHA1 is going to prove far more useful at |
| 23 |
that. |
| 24 |
|
| 25 |
|
| 26 |
>dev-java/antenna 2015-09-03 13:45:07Z monsieurp b4215f4 |
| 27 |
dev-java/antenna Sep 3, 13:45Z monsieurp b4215f4 |
| 28 |
|
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Kent |
| 33 |
|
| 34 |
KENTNL - https://metacpan.org/author/KENTNL |
Archives