On 3 December 2014 at 14:45, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> On Wed, Dec 3, 2014 at 2:45 PM, Philip Martin
> <philip.martin_at_wandisco.com> wrote:
>> Stefan Sperling <stsp_at_elego.de> writes:
>>
>>> On Wed, Dec 03, 2014 at 12:22:02PM +0000, sebb wrote:
>>>>
>>>> svn co --depth files https://svn.apache.org/repos/asf/subversion/trunk
>>>> subversion
>>>>
>>>> $ svn log -l 10 subversion
>>>> -- this works OK
>>>>
>>>> $ svn log -r {2014-11-30} subversion
>>>> ------------------------------------------------------------------------
>>>> $ svn log -r {2014-11-30T00:00:00} subversion
>>>> ------------------------------------------------------------------------
>>>
>>> Date search doesn't work on the ASF repository because svn:date properties
>>> of revisions aren't monotonically increasing.
>>>
>>> See the note at the very bottom of http://svnbook.red-bean.com/en/1.7/svn.tour.revs.specifiers.html#svn.tour.revs.dates
>>>
>>
>> That's correct, but it is not the complete story. The date search does
>> return a revision even if that revision is not "correct" is some sense.
>> However the date search works on the whole repository
>>
>> https://svn.apache.org/repos/asf
>>
>> so the revision produced will often be one which didn't change
>> /subversion/trunk. That means that an empty log is shown just like
>> it is for this
>>
>> svn log -r1643098 https://svn.apache.org/repos/asf/subversion/trunk
>>
>> Even when a repository does have strictly mototonic dates using log with
>> a single date will often show a blank log on non-root paths within the
>> repository.
>>
>
> So perhaps the user should have specified a range, instead of just one date?
>
> Like:
>
> $ svn log -r {2014-11-30}:HEAD subversion
>
> or:
>
> $ svn log -r {2014-11-30}:{2014-11-31} subversion
Doh!
Thanks, that works.
> --
> Johan
Received on 2014-12-04 14:13:26 CET