John A Meinel wrote:
> This is simply because bzr does not version anything but the executable
> bit. And in the short term, there is no plans to version more than that.
To expand a bit, new files are created with your umask, except for the
execute bit. When files are modified, whatever permissions they had on
disk are preserved.
The .gaim files you have after the merge are *new* files that bzr has no
reason to connect to the files that were previously under .gaim. The
.gaim.moved files are the files you previously had there.
It really has nothing to do with conflicts. Name the two directories
different things, and do a merge, and you'll get the same results.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John A Meinel wrote:
> This is simply because bzr does not version anything but the executable
> bit. And in the short term, there is no plans to version more than that.
To expand a bit, new files are created with your umask, except for the
execute bit. When files are modified, whatever permissions they had on
disk are preserved.
The .gaim files you have after the merge are *new* files that bzr has no
reason to connect to the files that were previously under .gaim. The
.gaim.moved files are the files you previously had there.
It really has nothing to do with conflicts. Name the two directories
different things, and do a merge, and you'll get the same results.
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFFO/ su0F+nu1YWqI0RA vVXAJ4/ tI2md6WXEKSAZiE KMj0ax8gpCgCfYP ss 8VbgqLuo=
C6CFjuGXWMoegxx
=bAMn
-----END PGP SIGNATURE-----