Comment 3 for bug 6391

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 6391] bzr diff -rNNNN is undocumented

On Wed, 2006-01-04 at 07:06 +0000, Martin Pool wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/6391
>
> Comment:
> On 3 Jan 2006, John A Meinel <email address hidden> wrote:
> > > This help doesn't tell me, in clear and simple terms, what "bzr diff
> > > -r1" will tell me about revno 1. I thought I could get the diff of what
> > > changed only in revno 1 with "bzr diff -r1", but that command appears to
> > > show something else.
> > >
> > > It seemed I had to do "bzr diff -r2934..2935" to see what changed in
> > > revno 2935, but I should have to specify only the revno I'm interested
> > > in to get diff information about that revno, not the number of the revno
> > > before it as well.
> > >
> >
> > The documentation does need to be updated.
> >
> > bzr diff
> > - Show the differences between the working tree and the last commit
> > bzr diff -rX
> > - Show the difference between the working tree and revision 1
> > bzr diff -rX..Y
> > - Show the difference between revision Y and revision X
>
> I agree the help message and the tutorial should be fixed.
>
> As a separate issue, I think we should change the behaviour to be what
> bradb expected, i.e. "bzr diff -r 40" is equivalent to 39..40. The
> behaviour of diffing 40 to the current version is less commonly used,
> and should be easy to get with "40..".

Eh? That seems awfully surprising to me, and not at all like CVS, svn or
baz.

Rob

--
GPG key available at: <http://www.robertcollins.net/keys.txt>.