date revisionspec not working as expected
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
High
|
Unassigned | ||
| Breezy |
Opinion
|
High
|
Unassigned | ||
Bug Description
Consider the following:
mkdir /tmp/bzrbug
cd /tmp/bzrbug
bzr co lp:~libadjoint/libadjoint/dolfin_paper
cd dolfin_paper
bzr log -r3
bzr log -r4
This shows that r3 was committed on the evening of the 18th of January, and r4 was committed on the afternoon of the 19th.
bzr cat -r3 dolfin_adjoint.tex > r3.tex
bzr cat -r4 dolfin_adjoint.tex > r4.tex
bzr cat -rdate:2012-01-19 dolfin_adjoint.tex > today.tex
I expect that -rdate:2012-01-19 will return r3, as that was the current revision at midnight on the 19th. However,
[pef@caoimhe:
011861d9334740c
a381c595b663d8b
a381c595b663d8b
today.tex is actually identical to r4, not r3 as expected.
This is on ubuntu natty (2.2.4-0ubuntu1).
| Changed in bzr: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| tags: | added: check-for-breezy |
| tags: |
added: revspec removed: check-for-breezy |
| Changed in brz: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Jelmer Vernooij (jelmer) wrote | #1 |
| Changed in brz: | |
| status: | Triaged → Opinion |
The behaviour is as documented: date: matches on anything *after* the specific date or time.
I'm close this, though it might be worth having a discussion about what people actually expect this to work like - since it might not be the same.