Hi, I have that same question. From bugzilla projects I remember that 
triggered by some expression in the commit message, that message was added 
to the ticket.

This is trac 1.0.3 with project-plugins.

I read
http://trac.edgewall.org/wiki/CommitTicketUpdater

Currently I have 1 git repository configured, which is a clone of some p4 
repository synced by 5-minutly cronjob doing 'git p4 rebase':

[trac]
repository_dir = /mnt/data/userspace/projectA
repository_sync_per_request = (default)
repository_type = git

Now on
http://trac.edgewall.org/wiki/TracRepositoryAdmin
I see there is only the configuration via [repositories] described. What is 
the difference. Is my configuration the old way, like "prior to 0.12, Trac 
synchronized its cache with the repository on every HTTP request" ?

For CommitTicketUpdater I have this configuration:

[components]
tracopt.ticket.commit_updater.* = enabled

[ticket]
commit_ticket_update_envelope = []
commit_ticket_update_commands.close =
commit_ticket_update_commands.refs = <ALL>
commit_ticket_update_check_perms = true
commit_ticket_update_notify = true

But committing a change with message...

[ticket #11]
Initial checkin

...does not do any change on the ticket #11. 

Does CommitTicketUpdater only work with the [repositories] configuration 
and post-commit? Does this hook work with changes coming in via git p4 
rebase?

Some question about Mercurial. There is written "Please note that at the 
time of writing, no initial resynchronization or any hooks are necessary 
for Mercurial repositories" but later there is a guide how to setup the 
hook for Mercurial. What is correct?

Best regards,
Massimo

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to