On Tue, Feb 17, 2009 at 3:54 PM, Randall Leeds <[email protected]> wrote:
> On Tue, Feb 17, 2009 at 10:14, Jeff Hammel <[email protected]> wrote: >> >> version of trunk that is effectively in the 0.11 series). Guaranteed it >> *will* break post-commit hooks, unless someone wants to write a plugin to, >> um, make this not so (shouldn't be hard, I would hope, though honestly git >> horrifies me). > > > In what sense would it break post-commit hooks? > I've never set up a trac instance, but poking around the trac.ini for the > melkjug project I see only the TicketChanger post-commit hook. From what I > gather from http://trac-hacks.org/wiki/TicketChangePlugin I don't see what > this plugin has to do with the chosen SCM backend. > > -R > If you look at http://trac.openplans.org/melkjug/admin/repository_hooksyou'll see some svn-specific stuff there, but assuming git has similar commit hooks I don't think it would be very hard to change this over. I'm happy to pair on this with Jeff and/or work on it alone for if and when the time is right. One other nit is that when I created our commits mailing list<http://www.openplans.org/projects/melkjug/lists/melkjug-svn-commits>I lacked sufficient foresight to give it a general name and address (fortunately I didn't make that mistake when I made [email protected] for Trac emails). I vote for retiring [email protected] when we switch and setting up a new melkjug-commits list, but if anyone has a strong opinion otherwise, I defer. P.S. All the enabled checkboxes on http://trac.openplans.org/melkjug/admin/repository_hooks are weirdly unchecked but the hooks are definitely working (at least the last time I tried "[closes XYZ]" in a commit message Jeff's awesome Repository Change Listener plugin (see blue:/usr/local/topp/trac/current/src/RepositoryHookSystem) kicked in and closed the ticket.
