Timeline reports too long

[Marthyn]

Why does this line go to 2024? It should go up until today's date i think cause you'll never write hours in the future.

[jurre]

You could write hours in the future, why not? It's supposed to go til the last entry btw, maybe someone entered something in 2024?

[Marthyn]

How can you write hours when you didn't work yet, that doesn't seem logical to me

--- Original Message ---

From: "Jurre" notifications@github.com
Sent: March 28, 2014 11:47 AM
To: "DefactoSoftware/Hours" Hours@noreply.github.com
Cc: "Marthyn Olthof" marthyn@live.nl
Subject: Re: [Hours] Timeline reports too long (#60)

You could write hours in the future, why not? It's supposed to go til the last entry btw, maybe someone entered something in 2024?

---

Reply to this email directly or view it on GitHub:
#60 (comment)

[jurre]

For instance because you know that you'll be at a client all day tomorrow from 9 to 5. I think it's super unnecessary to restrict this. We might add a warning that the entry is in the future, but we shouldn't forbid it.

[dkhgh]

fuck restrictions

[dkhgh]

fucking jesse @jejote

[jejote]

Gaaf!

Met vriendelijke groet,
Jesse Terpstra
Defacto
Zuiderpark 3
9724 AD Groningen
T +31 (0) 50 314 48 32
F +31 (0) 50 318 63 32

E j.terpstra@defacto.nlmailto:j.terpstra@defacto.nl
I www.defacto.nlhttp://www.defacto.nl
Defacto Software BV hanteert de algemene voorwaarden van de Fenit, gedeponeerd onder nummer 60/2003 bij de griffie van de arrondissementsrechtbank te Den Haag. KVK Groningen 02050992.
Van: dkhgh [mailto:notifications@github.com]
Verzonden: vrijdag 28 maart 2014 14:53
Aan: DefactoSoftware/Hours
CC: Jesse Terpstra
Onderwerp: Re: [Hours] Timeline reports too long (#60)

[screen shot 2014-03-28 at 14 52 05]https://cloud.githubusercontent.com/assets/4135610/2550168/35e85660-b680-11e3-8c63-9e8f6fdbf225.png

fucking jesse @jejotehttps://github.com/jejote

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/60#issuecomment-38920610.