Thank you very much for such an exhausive answer! I am just establishing the workflow now and trying to understand how things work in general. But if I find missing functionality, I will get in touch.
But I just got a little confused by wiki links. Suppose I want to add a link to external source and give it a title. [[https://juliankniephoff.wordpress.com/2011/03/27/use-objective-c-classes-in-cpp-opaquely-readably-and-safely|Bug]] What this expression becomes after formatting is concise "Bug?" in grey font. Apparently, the system thinks of the link being on localhost... Should I file a ticket? PS If I use single square bracket formatting with no pipe symbol, the hypertext is not seen at all - everything is displayed as it was written. On Sunday, January 10, 2016 at 3:28:00 AM UTC+6, Peter Suter wrote: > > Hi > Trac never modifies any files of or in Mercurial (or any other VCS). > Generally Trac does not interact with the VCS that much except for 1. > browsing and 2. updating tickets via commit messages: > > 1. Browsing files and viewing changesets etc. stored in the VCS. In my > opinion Trac is great at this. But if you disagree, this is entirely > optional. You can use Trac for tickets and not connect it to a VCS at all > if you want. > http://trac.edgewall.org/wiki/TracBrowser > http://trac.edgewall.org/wiki/TracChangeset > http://trac.edgewall.org/wiki/TracRevisionLog > > Some of Trac's VCS backends support storing cached VCS data in the Trac DB. > That can require resyncing the cache when the repository changes. > The Mercurial backend does not yet support this, so resyncing is not > required there as far as I know. > http://trac.edgewall.org/wiki/TracRepositoryAdmin#Repositorycaching > http://trac.edgewall.org/wiki/TracMercurial#Tocacheornottocache > http://trac.edgewall.org/ticket/8417 > > 2. Optionally Trac can be configured to react to new changesets that > contain certain keywords like "see #123" in the commit message for example. > That would add a comment to the Trac ticket #123. "fix #123" would > additionally mark that ticket as fixed. > http://trac.edgewall.org/wiki/CommitTicketUpdater > > > What exactly do you mean by "reversing a commit"? hg backout, hg strip? > Trac generally does not have a concept of changing repositories, except > for adding new changesets and resyncing cached data as described above. > So Trac would generally not react at all to "reversing a commit", except > as described above. > It certainly would not delete a bug report. > The closest I can think of would be this scenario: > * Someone commits Mercurial changeset AAAAAAAAAAAA which introduces a bug. > * Someone creates a Trac ticket #123 that describes this bug. > * Someone commits Mercurial changeset BBBBBBBBBBBB by backing out the > changes of AAAAAAAAAAAA, to fix this bug. > * The commit message of BBBBBBBBBBBB contains "fix #123". > * Trac detecs thits and automatically closes ticket #123 and adds a ticket > comment that references changeset BBBBBBBBBBBB. (As described above in > point 2. this is optional, and must be enabled / configured.) > > If you mean something like "hg strip" you would have to close the ticket > manually. (And resync the cache, but as mentioned in the case of Mercurial > there is no cache anyway.) > > Is there anything else you would like Trac to do with the VCS? > There may be a plugin, for example this one allows users to add / delete > entire Mercurial repositories in Trac: > https://trac-hacks.org/wiki/HgDirManagerPlugin > (I use this a lot. It's great for my usecase.) > > Or if you have advanced / special requirements it may be possible to write > one: > > http://trac.edgewall.org/wiki/TracDev/PluginDevelopment/ExtensionPoints/trac.versioncontrol.api.IRepositoryChangeListener#Examples > > Hope this helps > > > On 09.01.2016 13:52, xqbt wrote: > > Hey guys, I am new to trac, so bear with me. > Suppose I use Mercurial as my version control system. > So, a couple of questions that are on my mind: > 1) Does trac modify any of mercurial's files? > 2) If I reverse a couple of commits back in Mercurial, how does trac > react? Will a bug reported in the very new version go away (since we > reverted to some previous state)? > 3) Are there any caveats to know of when trac and Mercerial (or <your > favourite VCS>) work together? > Thanks! > -- > 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] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > Visit this group at https://groups.google.com/group/trac-users. > For more options, visit https://groups.google.com/d/optout. > > > -- 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 https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
