Date spec behavior inconsistent with docs

Bug #31276 reported by Matthew Fuller
2
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
Medium
John A Meinel

Bug Description

Documentation (partly corrected) and code comments suggest the revision spec range "date:today..date:tomorrow" should encompass all revisions today, but this fails:

% bzr log -rdate:today..date:tomorrow
bzr: ERROR: Branch BzrBranch(u'/tmp/bzr/dtest/') has no revision date:tomorrow

The range "date:yesterday..date:today" appears to be the correct usage to achieve the result.

Revision history for this message
Martin Pool (mbp) wrote :

Does this still require a code or documentation change?

Changed in bzr:
status: Unconfirmed → Needs Info
Revision history for this message
John A Meinel (jameinel) wrote :

Specifically on line 281 of revisionspec.py it says:
-r date:today..date:tomorrow

This should be changed to:
-r date:yesterday..date:today

Revision history for this message
John A Meinel (jameinel) wrote :

just a minor documentation fix. (It is correct in doc/specifying_revisions.txt, just updated bzrlib/revisonspec.py)

Changed in bzr:
assignee: nobody → jameinel
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.