bug in revision specs before:date: ?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned |
Bug Description
affects bzr
14:21 -!- bignose [<email address hidden>] has
joined #bzr
14:21 < bignose> my revspec fu is failing me
14:22 < bignose> 'bzr diff --revision
"date:2008-
14:22 < bignose> bzr: ERROR: Invalid revision-id {None} in
KnitRepository(
14:22 < bignose> presumably because it doesn't have any revisions *on*
2008-02-03
14:23 < bob2> what a friendly error
14:23 < bignose> but I'm specifically asking for all revisions *before*
that date, so I don't think it should spit an error
14:23 < bignose> $ bzr --version
14:23 < bignose> Bazaar (bzr) 1.1.0.candidate.1
14:23 < bignose> this is being run from an automated script, that
doesn't know what the last date in the branch is.
14:24 < bignose> how can I supply a "date:foo.
without that error?
14:24 < lifeless> bignose: strange, perhaps before:
14:25 < bignose> lifeless: I'm not sure what you're asking. the date
range I have is "date foo, through to before (foo + one week)"
14:25 < bignose> I have no way of knowing that (foo + one week) is the
last date, without a lot of mucking about
14:25 < bignose> s/is the last date/is *past* the last date/
14:25 < lifeless> bignose: I'm saying that if you don't know of a commit
that will match, you should ask for the first commit before the date you
want it to match
14:26 < bignose> lifeless: that's exactly why the range I gave above is
bounded by "..before:
14:26 < lifeless> bignose: you're not using before on both sides though
are you?
14:27 < bignose> no.
14:27 < lifeless> which is what I was suggesting
14:27 < bignose> but, AFAICT, it's the upper bound that causes it to
fail
14:27 < bignose> because the range "date:2008-
14:27 < lifeless> oh
14:27 < lifeless> in which case, welcome to bugs
14:27 < lifeless> please file one :)
--
GPG key available at: <http://
I'm also ran into this