bzr branch --basis disabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Robert Collins |
Bug Description
From: <email address hidden>
Subject: Re: [PATCH] checkout --help
Date: 7 May 2006 3:27:27 AM
To: <email address hidden>
Cc: <email address hidden>
Robey Pointer wrote:
On 5 May 2006, at 20:57, John Arbash Meinel wrote:
Robey Pointer wrote:
Just noticed this today: Doing 'bzr checkout --help' still documents a
'--basis' option which is not accepted and wouldn't do anything even if
it was. Attached patch removes the documentation lines and comment.
robey
Rather than removing the option, we could actually re-activate the
functionality. 'bzr branch' supports --basis, and checkout is very
similar to 'bzr branch'. It does a few things differently (creates a
branch, and then does 'bind' which does a pull, versus doing 'sprout').
But honestly, we could do a standard sprout, and then do the bind.
If someone knows how to use --basis, it seems like a decent performance
improvement to not have to copy everything from the remote location.
We could resurrect it post-0.8 -- the help text will always be in the
branch history. ;) It's just a little confusing to see it now when the
--basis option doesn't actually exist.
robey
I'm fine with handling it either way. I don't know if people use --basis
a lot. I generally don't, but mostly because I always used "bzr branch
local newlocal; cd newlocal; bzr pull --overwrite --remember remote".
Now with repositories it is even less important.
Because either I already have a copy of the remote files which will be
re-used. Or I need to get everything anyway.
Changed in bzr: | |
assignee: | nobody → lifeless |
status: | Unconfirmed → Fix Committed |
Changed in bzr: | |
status: | Fix Committed → Fix Released |