Matthew A. Nicholson wrote:
I felt it would be usability deficiency to force users to always
specify the whole url when switching to another branch, so I went
with shorter names.
I think we'd need some form of short/long branch names or some user
aliases for the branch names or a project name (the long stuff) and a
branch name within the project. The goal would be to specify the long
stuff with the url only once...
Insted of doing com.domain.branch I name my branches as
domain.com/branch. It makes more sense to me.
I've been using "monotone -b branch update REV" quite often to switch my
working copy to a different branch. That is why I do not want the branch
to be too long.
BTW: Is there an easy way to switch the working copy to a different
branch? I thought that "monotone -b new_branch update" (without the
explicit REV arg) would do the trick but it does not :(. I have to first
find out the head of the branch by "monotone -b new_branch heads" and
then copy&paste the REV.
So, if the "domain.com" part of the branch name was stored in MT/options
seperately from the "branch" and I could use just the "branch" part when
switching to different branch, that would cetrainly motivate me to use
the globaly unique branch names.
Zbynek
--
http://zw.matfyz.cz/ http://robotika.cz/
Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic
_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel
