--strict as default

[Martin Pool]

2010/1/15 Jelmer Vernooij <jelmer.vernooij at canonical.com>:
> At the moment there are several commands that default to --strict. While
> it seems to be a good idea to make the user aware of uncommitted changes
> by default, I think it should be a warning rather than an error by
> default. Most people I've talked to also seem to prefer no-strict by
> default.

I agree.  A patch to change it back for 2.1 would be welcome.

Eventually we may want error/warn/nothing, as checking whether there
are uncommitted changes might take nonnegligible time.
-- 
Martin <http://launchpad.net/~mbp/>