Pushing several local commits to a remote branch

[Martin Pool]

On 27 June 2010 02:26, Eli Zaretskii <eliz at gnu.org> wrote:
> The Emacs repository still uses sftp, which is slow.  So much so that
> one of the most active contributors to Emacs says he thinks twice
> before trying to do any development work, see
> http://lists.gnu.org/archive/html/emacs-devel/2010-06/msg00989.html.
>
> Given this sad state of affairs, I thought that perhaps using
> "bzr ci --local" for several changes followed by a single push
> could make the life of a contributor easier, as the overhead of
> the sftp protocol would be sustained only once.
>
> The question is, since the master repository is on Savannah, is
> there any possibility to screw up history either on the master
> branch or in the local branch bound to it?

I realize emacs wants to ask people to use bzr in a particular
semicentralized standardized model and I realize I am not up to date
on the whole history of it.

Still: why not actually make full-fledged branches locally, merge into
a local copy of trunk, then push that?  Then people should never or
rarely need to block waiting for network traffic.

-- 
Martin