rename push to publish

[Wouter van Heyst]

On Sun, Feb 12, 2006 at 04:09:44PM +0200, Jari Aalto wrote:
> John A Meinel <john at arbash-meinel.com> writes:
> 
> >> So aaron suggested renaming push to publish and using that -d for anyone
> >> that wanted the inverse of pull behaviour (such as setting the remote
> >> 'parent' to $pwd, which IMO is nuts for a copy of my branch on a
> >> webserver.
> >
> > If we continue to have 'push' able to create branches, then I think it
> > should be called 'publish'. Ultimately, I think this functionality
> > should be in 'branch' not in 'push'.
> 
> Please "no more new commands". It makes sense to extend the functionality
> that's already there, so something like
> 
>        push --create ...
> 
> or other modifier options woul be better than any new command.

Aiui, there wouldn't be a new command. Push would disappear, and there
would then be pull (-d) and publish. On publish, jblack brought up (in
the context of repositories), publishing an entire directory of
branches. Paraphrased that becomes:

    bzr publish ~/branches/work sftp://canonical.server/

This can easily be done as a plugin like update-mirrors, but is it
possible to have the 1 branch/multiple branches cases work from the same
push/publish?

Wouter van Heyst