Re: Gnus overrides.texi and WEBHACKDEVEL

[Eli Zaretskii]

> From: "Stephen J. Turnbull" <address@hidden>
> Cc: address@hidden,
>     address@hidden,
>     address@hidden
> Date: Mon, 07 Feb 2011 02:52:45 +0900
> 
> But it's a simple, generic observation: if you have some changes that
> should be pushed, and others (that may be worth preserving) that
> should not be pushed, use a branch to work in.  Then cherrypick the
> changes to your integration workspace (which can be a branch or a
> checkout).  Finally push the commits from the integration workspace.

If this is what you had in mind, then it's still manual work, and
thus prone to errors.  I can do the same in a bound branch with
"bzr ci FILE1 FILE2 ...", thus "cherrypicking" only what should be
pushed.

The original problem was that some people do not pay attention to what
"bzr status" says, and just do a "bzr ci", which pushes all the
modified files.  I guess there's no way around vigilance.  Which is
fine with me.

Thanks.