RFC: naming of the 'record' command in the loom plugin

[Goffredo Baroncelli]

On Monday 25 February 2008, John Arbash Meinel wrote:

> I honestly haven't used it a lot, so I'm not sure what commands are used all 
the
> time (shelve/unshelve) versus infrequently (shelf list, shelf delete).
> 
> Looking at the list of commands in "bzr help loom" it breaks down into:
> 
> ~  loomify
> ~  record
> 
> ~  create-thread
> ~  down-thread
> ~  up-thread
> ~  combine-thread
> 
> ~  revert-loom
> ~  show-loom
> 
> record actually seems the odd-man-out in this case. And "commit-loom" seems 
to
> be a closer match. Since all the other commands have either 'thread' 
or 'loom'
> in their names.


In my opinion, I think that we have two choises:
1) commands prefixed by loom, or separated by an hypen like
   * bzr loom createthread
   * bzr loom-create-thread
   [..]

That can be useful during the initial develop phase in order to better 
highlight the plugin.

2) a short form like:
   * bzr lcreate
   * bzr lup
   [...]
That is more conformatble during the day by day work. 

BTW mercurial uses a sismilar scheme for "mq" (qinit, qdiff....)


-- 
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack at inwind.it>
Key fingerprint = CE3C 7E01 6782 30A3 5B87  87C0 BB86 505C 6B2A CFF9