[PATCH] Implement --strict flag for commit
John Arbash Meinel
john at arbash-meinel.com
Mon Oct 17 22:49:59 BST 2005
Aaron Bentley wrote:
> Michael Ellerman wrote:
>
>>>Y'all,
>>>
>>>Here's a patch to implement strict commits (no unknown files allowed).
>
>
> Cool. It might be nice for users to be able to make this their default,
> if they're really into strictness.
>
Perhaps as a per-branch setting? Otherwise, I certainly agree. In
general, I would like to see config options (like bzr log --forward
--short) be settable somewhere. Right now I just write a plugin so that
the commands act the way I want them to.
>
>>>The TODO mentions not allowing deleted files, but I didn't know what that
>>>meant so I just left it. Any ideas?
>
>
> Normally, if you delete a file, commit will treat is as removed. Not
> allowing deleted files would mean having to "bzr remove" every file
> before deleting it.
We could update "bzr remove" to act like "cvs remove" which traverses
the tree, and marks missing files as deleted.
I wouldn't mind giving it a flag to do this, perhaps "bzr remove
--recursive" or "bzr remove --all-missing"
>
> Aaron
John
=:->
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051017/f0b3cb28/attachment.pgp
More information about the bazaar
mailing list