[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Gnus overrides.texi and WEBHACKDEVEL
From: |
Eli Zaretskii |
Subject: |
Re: Gnus overrides.texi and WEBHACKDEVEL |
Date: |
Sun, 06 Feb 2011 23:21:58 +0200 |
> From: "Stephen J. Turnbull" <address@hidden>
> Cc: address@hidden,
> address@hidden,
> address@hidden
> Date: Mon, 07 Feb 2011 04:20:39 +0900
>
> > 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.
>
> No, there isn't. However, committing all changes, using
> branch-per-feature in your workflow, and using appropriate commit
> messages for coherent changesets can reduce the amount of effort
> needed to implement vigilance.
True.
- Re: Gnus overrides.texi and WEBHACKDEVEL, (continued)
- Re: Gnus overrides.texi and WEBHACKDEVEL, Stephen J. Turnbull, 2011/02/06
- Re: Gnus overrides.texi and WEBHACKDEVEL, Eli Zaretskii, 2011/02/06
- Re: Gnus overrides.texi and WEBHACKDEVEL, Stephen J. Turnbull, 2011/02/06
- Re: Gnus overrides.texi and WEBHACKDEVEL, Eli Zaretskii, 2011/02/06
- Re: Gnus overrides.texi and WEBHACKDEVEL, Stephen J. Turnbull, 2011/02/06
- Re: Gnus overrides.texi and WEBHACKDEVEL, Eli Zaretskii, 2011/02/06
- Re: Gnus overrides.texi and WEBHACKDEVEL, Stephen J. Turnbull, 2011/02/06
- Re: Gnus overrides.texi and WEBHACKDEVEL,
Eli Zaretskii <=