Ticket #8 (new enhancement)
Pull in changes automatically from somewhere to decrease lock chances
| Reported by: | marcel@… | Owned by: | moschny |
|---|---|---|---|
| Priority: | minor | Component: | tracmtn |
| Version: | Keywords: | ||
| Cc: |
Description
Another idea perhaps to decrease locking problems?
Many trac+monotone installs probably use a cron like solution to pull revisions from a database which is used by a group of people to push to. That is, one push.db to which developers normally push their changes and a mtntrac.db which is used by the plugin in trac.
At times this causes cron errors because the db is locked. Would it be possible to have the mtn plugin pull changes in from somewhere configurable, at a configurable interval to reduce lock problems?
Attachments
Change History
Note: See
TracTickets for help on using
tickets.
