I'm afraid you need to do some scripting:
git log --format="%ad %H" --date=iso | sort | ruby -ane 'date = $F[0] ; hash = $F[3] ; puts hash if ("2013-08-23".."2013-09-26").cover?(date)'
gave to me:
3eddb854eaea971e9a60147153f0f3c9be4f1a5a
dfeefd4715c4fddef0957c5aff238c525bb1def6
db654badb97f3784286171d4645e9face6a42865
62cdba07e6ae0cd28752491a83f584d3e18a5619
7643a0458a54200f8944583d66c089d63c1bf688
23b720852a36e959d0f45f9d11f05d4aa7ee0cb9
f729ec9c5bf37ee0284a8db47cbc79a0b53145bb
bc2d647ae86fbff1246ba163a5a99d25ed2f3523
a0752b3cbae39698449be953153ddaafe35c054c
8e88fffc75cbdda333c86cb4f5eb9b5b30263c27
Unfortunately, git log 3eddb854eaea971e9a60147153f0f3c9be4f1a5a..8e88fffc75cbdda333c86cb4f5eb9b5b30263c27
is not guaranteed to work because those commits may be in different branches.
Let's explain what I did:
--format="%ad %H"
– format log as author_date commit_hash
lines
--date=iso
– dates in YY-mm-dd HH:MM:SS
format
sort
– Unix command which sorts lines alphabetically; it's suitable to sort dates in ISO format
ruby -ane
– execute ruby script. -n means execute for every line, -a split those lines and put fields into $F
array, -e precises script to execute
("2011-02-23".."2011-02-26").cover?(date)
– create range from two strings and check if date fits it inclusively (in the meaning of alphabetical order, we were not parsing those dates)
I have no idea what to do next (to give you nicer log), but glad to move you to this point.