[Patch] bzr status doesn't handle revision
John A Meinel
john at arbash-meinel.com
Tue Sep 13 05:04:01 BST 2005
Robey Pointer wrote:
>
>> John A Meinel <john at arbash-meinel.com> writes:
>>
>> | bzr diff -r 1..revid:john at arbash-meinel.com--blah.de.blah.deblah
>> | bzr log -r date:+yesterday..date:-tomorrow
>> |
>> | (The syntax for the date code is a little bit odd, but the above would
>> | print out all the changes from yesterday through today, up until just
>> | before tomorrow).
>
>
>
> Yes, that date syntax is difficult. :)
>
> How about using [start,end) convention there and removing the "+" and
> "-"? For non-math-geeks, [start,end) is the same as python slices: the
> start point is included but the end point is not.
>
> Then "date:yesterday..date:tomorrow" would mean "everything from the
> beginning of yesterday, right up to -- but not including -- the
> beginning of tomorrow" or "11-Sep-2005 0:00:00 .. 12-Sep-2005
> 23:59:59.999999".
>
> robey
>
The problem as it stands is how the revision parser works, which
generally treats each entry separately, so it doesn't know if you are
looking for the beginning of a date range, or the end of one. The +/-
change the meaning slightly, though I believe doing:
bzr log -r date:yesterday..date:tomorrow
Would almost work. (tomorrow would fail because there are no revisions
which match that date. Hence you have to specify the -tomorrow so that
it looks for the first revision before the specified time).
The other possibility would be to extend the revision parsing, so that
you could pass more hints into the system. But right now, each side of
the '..' is handled in it's own little world.
John
=:->
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050913/d256ef88/attachment.pgp
More information about the bazaar
mailing list