UI confusion / consistency

Nicholas Allen nick.allen at onlinehome.de
Thu Nov 22 21:51:32 GMT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> 
> That is true of most bzr commands; if you want to act on the CWD, you
> can easily supply ".".  If "." were the default, there would be no way
> of easily getting the other behavior.

True but it's easy to forget this. I like the idea that I can CD into a
directory and know I'm only affecting that directory down.
> 
> And philosophically, it makes sense to consider the whole tree by
> default. 

I'm not so convinced. Many commands work on subsets of the complete data
(any command that can take a list of files or dirs as arguments) and so
I think . as default makes sense in these cases.

Perhaps there could be some way to refer to the root of the branch as a
bzr command?

eg bzr commit `bzr root`

or perhaps there are better ways. I tend to cd to the root when I want
to work on the whole branch anyway. Maybe that's just because I'm used
to CVS, subversion and other Unix commands that work on CWD.

 We are a whole-tree tool, and believe that changes to one file
> may often affect files in other parts of the tree.  If, say, commit
> defaulted to the CWD, there would be a lot more commits that failed to
> commit all the necessary changes.

I really like to be able to commit changes in a sub dir. It's something
I seem to need to do. To forget the . and commit the whole tree is also
slightly annoying (not as much as a revert though!).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHRfnk1+i51gqqEGkRAsRuAJ94B62ODqPWf8BzPGqNEfttmcnnswCgpTX1
/QIcHmzdir1UMFFtz7Apkg8=
=sGIp
-----END PGP SIGNATURE-----



More information about the bazaar mailing list