Refactoring of Branch.rename_one
Johan Rydberg
jrydberg at gnu.org
Sun Sep 25 13:13:04 BST 2005
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
What do you people think of moving out the some of the code from
Branch.rename_one to the UI (i.e., builtins.py). My gut feeling tells
me that Branch.rename_one should only be an operation on the inventory
and not also on the working directory. Also, this makes things a lot
harder for tools like ``tailor'', which actually does the rename
itself.
It might be sufficient to just add a flag to rename_one that specifies
that the rename has already been done.
~j
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFDNpRQ3CqIy3K3X2ERAnZzAJ4xDbZ820XTcSBdKTCHnn6tj6IPCACfXRcA
h7PzporvJa5pVkjVHtENFm8=
=KgJy
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list