"log -rdate:" and "log -cdate:"

[Maritza Mendez]

Wow. I guess my eyes zoomed in on date and I never noticed before.  My
bad.  The points Eli and Martin make remain valid I think.  Thanks.

~M

On 11/29/10, John Arbash Meinel <john at arbash-meinel.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> ...
>
>> Martin,
>>
>> Thank you for your openness to discussing this aspect of revisionspecs.
>> My team and I have experience similar to Eli's post.  I cannot
>> articulate it any better than this: dates seem to be special.  People
>> (including me) seem to have intuitive expectations when specifying a
>> date different from the simple (and well defined) semantics of the date:
>> syntax.  So I think your third bullet (log+filter) is especially
>> insightful.  I already do something like this manually and often.  A
>> trivial example is to reverse the "sense" of 'date' to pick the "latest
>> before" instead of the "earliest after" revision for the upper end of a
>> revspec range.  I understand your third bullet as meaning "leave
>> revspecs alone but allow for a thin interpretive layer" which is both
>> good for the stability of bzr and fulfills the "batteries included"
>> vision.  I realize there are efficiency implications, but efficiency
>> counts most when the user gets what she expects.  :)
>>
>> ~M
>>
>
> Note that you can get 'latest before' by using "before:".
> John
> =:->
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Cygwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkzz9V4ACgkQJdeBCYSNAAPIjACgpUOHYehL/6KNhScploPM9zS7
> FWAAoNAGDbvNcx/TC/gAGSNbtQX0BrLk
> =ZGen
> -----END PGP SIGNATURE-----
>