[PATCH] Implement --strict flag for commit

[John A Meinel]

Aaron Bentley wrote:
> David Allouche wrote:
>
>>>Case A: The Contributor will always submit changes that are valid to the
>>>Maintainer, since the Contributor is stricter than the Maintainer.
>>>Social peace ensues.
>
>
> I disagree that either strict or loose can cause the contributor to
> submit changes that are invalid to the maintainer.  --strict only
> applies to the working tree.
>
> Aaron

I think David is referencing 2 different ideas. One is to have a "commit
--strict" such that a test suite is run before a commit is accepted. And
the other is a --strict that just doesn't allow bogus files (not
actually added) to exist in the working tree.

The later form (the one that is actually presented here), really doesn't
have an effect on the Maintainer, since he should never see the bogus
files (though if they were needed, it might mean that the maintainers
checkout wouldn't work).

The former form means if you were looser than the maintainer, you could
commit code that wouldn't pass muster.

John
=:->
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051018/a3f9c44f/attachment.pgp