Comment 11 for bug 135234
Revision history for this message
| Aaron Bentley (abentley) wrote Re: [Bug 135234] Re: Checkout should record relative paths (dir move problem) | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
On 03/28/2010 05:50 AM, Jari Aalto wrote:
>> Have you considered the case where the checkout is moved, but the bzr
> branch stays in the same place?
>
> I think the file level operations should work without hick-ups:
>
> $ mv repo.bzr /other/
A key benefit of checkouts is that they allow you to separate your
working tree from your repository. In such a situation, the specified
command will *always* break things.
> This way tarring up files and directories. moving them around, works
> like with any other directory.
>
> I think it is reasonable to assume that the way user writes the URL to
> clone is preserver "AS IS".
I don't. I think it's very easy for users to screw that sort of thing
up. We have thought about the implications, and the user usually hasn't.
We have always recorded interpreted values everywhere. On *nix, we
can't avoid this, because the shell does some of the interpretation.
I think we should not introduce inconsistency here.
Aaron