How to get the diff between two arbitrary remote revisions?

[Jan Hudec]

On Mon, Nov 21, 2005 at 09:23:42 +1100, Martin Pool wrote:
> On 18 Nov 2005, Jan Hudec <bulb at ucw.cz> wrote:
> > > > bzr checkout -r 1234 /repository/some/branch
> > > > <hack, hack, hack>
> > > > bzr commit -b /repository/new/branch
> > > 
> > > I'd rather see the -b flag on checkout, but nothing's set in stone yet.
> > 
> > I may not want to commit to it, in which case I shouldn't need to name it.
> > And later I may realize I do want to commit to it after all, so I think the
> > flag should be available on commit. It can be available on checkout as well.
> > 
> > Of course if I did not give -b to checkout and don't give it to commit
> > either, it should complain about "Branch needs to be named. Use -b option"
> 
> So this 'commit -b' would be similar in effect to copying the directory
> to a new name, and committing in the new copy?

No, it would not. It would create a new _archive_ branch.

> There is a workwhile use case of someone doing some work and then
> deciding that it ought to be on another branch, possibly a newly created
> branch.  Baz accomodates this with the switch command.  

Yes, it is possible to create an archive branch, switch to it and commit.
I just proposed making it a bit easier. Just a low priority wishlist item.

-- 
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051122/04338d40/attachment.pgp