Better name for dpush wanted

[Nicholas Allen]

Stephen J. Turnbull wrote:
> Nicholas Allen writes:
>
>  > I don't understand the problem with the number of commands. If you
>  > reduce them then you add more options to the remaining commands and then
>  > they aren't as discoverable.
>
> I don't really think have a half-dozen variations on "ls" all of which
> have very different names from each other is a big improvement over
> having one "ls" command whose one-liner is
>
> ls   list selected files known to bzr or in the tree
>
> If you want to know if bzr can tell you what files you should have
> that you don't after a misadventure with 'rm *', it may not be obvious
> that "missing" is the command you want, and with 144 fully packed
> lines in the help, I think it's easy enough to miss "missing".  But if
> you know that "ls" exists and has options, I don't think it's hard to
> look at "bzr help ls" and find "bzr ls --missing".
>   

I agree that it would be nice that ls had these options. But I'm not
really sure if I would want the existing commands to be removed in that
case.
> That's a matter of opinion of course, and I know that some of the
> suggestions went too far.
>
>  > I think Bazaar's done a pretty good job of coming up with names for
>  > commands that represent common concepts.
>
> Sure.  The problem isn't really that there are too many names, it's
> that there are too many core concepts, some of which (like init-repo)
> should not need to be exposed to ordinary users.
>   

init-repo is optional but offers space saving and performance
improvements. You could use Bazaar without knowing about this command so
what's wrong with having a command to do this? It makes it more
discoverable. I like that Bazaar has the concept of one branch per
directory and a repository where a bunch of branches can be stored more
efficiently. I don't see it as too many concepts being exposed. In fact
I think it helps with the learning curve as users start with a simple
concept of one branch per directory and then learn about repositories
later for optimisation reasons. But still I think it would be great if
Bazaar offered some automatic revision cache. This would reduce the need
to have shared repositories so users could learn about them later and
would make Bazaar seem much faster in the common case when performing
network operations.

Nick