Behavior of 'rm' and 'mv' under bazaar
John Arbash Meinel
john at arbash-meinel.com
Wed Oct 13 19:37:19 BST 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/13/2010 12:59 PM, Mark A. Flacy wrote:
> On Wed, 2010-10-13 at 11:31 -0500, Neil Martinsen-Burrell wrote:
>> On 2010-10-13 09:45 , Tom Browder wrote:
>>> But, and this is different from subversion, c is shown as a new file
>>> which MUST be committed if I want it in the current mainline.
>>
>> This is true. Relative to the previous revision, c is a new file. The
>> fact that there was a file named c in a previous revision isn't relevant
>> to Bazaar. In Bazaar, there is (currently) no way to indicate that the
>> file c in this revision is the same as the file with the same name in a
>> previous revision. (Internally to Bazaar they have different file IDs.)
>
> I believe that Bazaar used to support the Gnu Arch concept of a tag
> within the beginning or end of a file which positively identified the
> file. I do not know if bzr supports that idea. (I can think of reasons
> not to do so.)
>
> http://newsgroups.derkeiler.com/Archive/Comp/comp.emacs/2008-04/msg00018.html
>
bzr itself has never supported them. We've talked about it, and as long
as you implement a cache, so that you don't have to read the content of
every file, it could still perform well. (If a file matches your mtime
cache, then you can assume the file-id hasn't changed as well).
But for now, we don't support it. And it isn't in the roadmap to do so.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAky1/F8ACgkQJdeBCYSNAAOowwCeJ8HpwJHGZQfXFWmzAIFPiCte
4xUAoIB1BpmZzc3PgwIDpmiky5l4HGsE
=kSEr
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list