Merge lp:~parthm/bzr/538868-message-for-heavy-checkout into lp:bzr
Status: | Superseded | ||||||||
---|---|---|---|---|---|---|---|---|---|
Proposed branch: | lp:~parthm/bzr/538868-message-for-heavy-checkout | ||||||||
Merge into: | lp:bzr | ||||||||
Diff against target: |
336 lines (+139/-23) 8 files modified
NEWS (+3/-3) bzrlib/builtins.py (+0/-5) bzrlib/recordcounter.py (+65/-0) bzrlib/remote.py (+2/-1) bzrlib/repofmt/groupcompress_repo.py (+23/-4) bzrlib/repository.py (+6/-4) bzrlib/smart/repository.py (+40/-4) bzrlib/tests/blackbox/test_checkout.py (+0/-2) |
||||||||
To merge this branch: | bzr merge lp:~parthm/bzr/538868-message-for-heavy-checkout | ||||||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
John A Meinel | Needs Resubmitting | ||
Martin Pool | 2nd review | Needs Information | |
Vincent Ladeuil | Approve | ||
Gary van der Merwe | Approve | ||
Review via email: mp+24483@code.launchpad.net |
This proposal has been superseded by a proposal from 2010-05-14.
Commit message
(parthm) heavyweight checkout now indicates that history is being copied.
Description of the change
=== Fixes Bug #538868 ===
For heavyweight checkout show a message showing that history is being copied and it may take some time.
Sample output:
[tmp]% ~/src/bzr.
Copying history to "foobar". This may take some time.
bzr: interrupted
[tmp]% ~/src/bzr.
Copying history to "trunk". This may take some time.
bzr: interrupted
The only ugliness I see is in the off case that to_location already exists. In this case the output is:
[tmp]% ~/src/bzr.
Copying history to "trunk". This may take some time.
bzr: ERROR: File exists: u'/home/
It would be ideal if the "copying history" message is not shown. I suppose thats not too bad though. I had a early failure fix for this but haven't put it in considering that bzr works across multiple transports.
+ # Fail early if to_location/.bzr exists. We don't want to
+ # give a message "Copying history ..." and then fail
+ # saying to_location/.bzr exists.
+ to_loc_bzr = osutils.
+ if osutils.
+ raise errors.
+
Thanks, this is a very nice bug to fix.
I would prefer the message came out through trace or the ui factory
than directly to self.outf, because that will make it easier to
refactor out of the cmd implementation, and it's more likely to
automatically respect --quiet. You might then be able to test more
cleanly through TestUIFactory.