[RFC] tell users to upgrade knit branches

[Matthew D. Fuller]

On Wed, Mar 26, 2008 at 06:33:59PM -0400 I heard the voice of
Aaron Bentley, and lo! it spake thus:
> 
> Can I suggest that if we emit a warning, we do it when the
> repository is write-locked, and that we provide a config option to
> disable such warnings?

I made an abortive attempt at the latter back when bzr started
bleating about pre-dirstate WT's; the branch is probably still on LP
considering how often the branch list is cleaned out.

It should be cheerfully ignored in implementing a config option
though; what's really needed [from somewhat vague memories, compounded
by my own vague understanding of bzrlib] is moving where the warnings
are generated somewhere closer into the formats so that more
information is ready at hand.  Doing it where the warnings currently
come from[0] makes it either not configurable in the branch at all, or
re-open the branch.



[0] Well, where SOME of the warnings come from.  The warnings used for
    WT3 come from a rather general facility to issue warnings, but the
    warnings for weave branches are hardcoded in the weave
    implementation...   consistency would be nice.


-- 
Matthew Fuller     (MF4839)   |  fullermd at over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.