News for hackers. Stuff that matters.
Re:Best GitHub repositories by coherentpony on Thursday August 07, 2014 @06:26AM (#8146981)
Because perhaps someone wants to look at trends over time. Doing it this way means that you don't have to scour through the git history to get your data. Also, scouring the git history, as you suggest, assumes that each commit corresponds to exactly one daily update. What if there are commits that fix typos or other errors? How do you programmatically skip over those?

Pushing a new document every day is the correct choice here.

Re:Best GitHub repositories by Grue3 on Thursday August 07, 2014 @07:06AM (#8147056)
No, the correct choice would be using one file and tags for each date. To fix a typo you just go to appropriate tag and make a commit.
Re:Best GitHub repositories by thu on Thursday August 07, 2014 @08:58AM (#8147435)
"correct" w.r.t. what ? A checkout (or a tarball as offered by GitHub) of the repo is all those files, which is probably what most people want.
Re:Best GitHub repositories by coherentpony on Thursday August 07, 2014 @08:58AM (#8147437)
I didn't think about tags. That's a fair point.