Re: Gnus overrides.texi and WEBHACKDEVEL

[Eli Zaretskii]

> From: "Stephen J. Turnbull" <address@hidden>
> Cc: address@hidden,
>     address@hidden,
>     address@hidden
> Date: Sun, 06 Feb 2011 23:40:25 +0900
> 
> Eli Zaretskii writes:
>  > > From: "Stephen J. Turnbull" <address@hidden>
>  > > Cc: Ted Zlatanov <address@hidden>,
>  > >     address@hidden,
>  > >     address@hidden
>  > > Date: Sun, 06 Feb 2011 15:49:08 +0900
>  > > 
>  > > Eli Zaretskii writes:
>  > > 
>  > >  > By "user" I _did_ mean developers in this case.  How do we prevent the
>  > >  > danger of committing a modified file?
>  > > 
>  > > By using a real branch instead of a checkout.
>  > 
>  > Are you saying that "bzr push" will somehow catch these problems where
>  > "bzr commit" in a bound branch doesn't?
> 
> Of course not.  I'm saying that one needs to use an appropriate
> workflow to get the desired behavior.

So what workflow will avoid this danger?  Can you show the commands in
that workflow for when a changeset is ready to be committed to the
master repo?