Jens Nilsson

Ran a small test with specifying it that way just now.

On Apr 11 2013 I have 6 commit in a repo.

Using git log --pretty=format:"%an - %ad -> %s" --since=87.days.ago --until=86.days.ago:

Jens - Thu Apr 11 08:01:10 2013 +0200 -> Remove donate link in readme
Jens - Thu Apr 11 07:57:32 2013 +0200 -> Updated readme
Jens - Thu Apr 11 00:17:48 2013 +0200 -> Updated readme
Jens - Wed Apr 10 23:49:18 2013 +0200 -> Added a small instructions section to markdown reame
Jens - Wed Apr 10 23:45:37 2013 +0200 -> Added function to render the map in a theme.

3 commits I'm after and a couple of unwanted ones from the day before.

Using git log --pretty=format:"%an - %ad -> %s" --since=86.days.ago --until=85.days.ago:

Jens - Thu Apr 11 20:55:14 2013 +0200 -> Added link to the wordpress.org plugin page
Jens - Thu Apr 11 20:51:13 2013 +0200 -> Added some more tags
Jens - Thu Apr 11 20:50:33 2013 +0200 -> Added screenshot descriptions

Just 3 commits from the date I'm after (I have 0 commits in this repo on the 12th).

Based on the timestamps of the commit messages, this makes me think that the --since and --until flags flags include commit-messages since/until 12:00 respectively.

I would like to be able to use those, but I noticed that for some reason they didn't return all commits, there was always 1 missing.

Tested with --since="2013-07-04 00:00:00" --until="2013-07-04 23:59:59"