Changesets feature complete

[Michael Ellerman]

On 5/20/06, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:
> Hi all,
>
> Looks like changesets are feature-complete.

Nice. Now that you've done all that hard work I'm going to proceed to
hit you with bugs and niggles ;)

If you run 'bzr cset' without redirecting you get the progress bars
interferring with the changeset output. I imagine it's just a matter
of buffering the cset output until the pbs are finished?

# bzr cset -r 0..-1
just gives me the last revision as a changeset, I would have expected
the entire history?

# bzr cset -r 0..
bzr: ERROR: Invalid revision-id {None} in
KnitRepository(u'/home/michael/src/bzr/repo/.bzr/')

# bzr cset -r 1..-1 > patch

I was expecting this to be equivalent to the concatenation of all the
individual changesets between 1 and -1. But it's not quite. The last
changeset seems to contain stuff from way back in the past, which is
confusing because it means the message doesn't accord with the diff.
I'm not sure if that's the expected behaviour or not.

The cset is too big to attach, but if you do 'bzr cset -r 1..-1' on my
shelf branch you'll be seeing what I'm seeing.

cheers