Request: post-commit hook needs more info

John Arbash Meinel john at arbash-meinel.com
Wed Oct 17 23:21:51 BST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Collins wrote:

...

> 
> Indeed, but branch can still have policy about what changes it will
> accept, and about notifying changes that have occured.
> 
> I don't think a Branch hook should ever take a tree. 
> 
> -Rob
> 

Well, a very specific use case for post-commit is to write out a ChangeLog. And
without having a Tree, you don't know where to put it.

The branch is not a good place, since it is completely wrong for a lightweight
checkout.

To *do* a commit you must have a Tree. (commit.py requires it)
So it seems reasonable that the *policy* is set by the Branch (what is allowed
here), but the hooks can have access to the location where the files are being
changed.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHFor+JdeBCYSNAAMRAsBoAJ4zMhQFsv7pUueKsMSNzsN7xON1MwCfa9Ki
TK63YS9YQu27pleCiFHuZx0=
=feo2
-----END PGP SIGNATURE-----



More information about the bazaar mailing list