[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: The NOTATION for trac link for Ticket

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-09-20 17:46:57 CEST

On Sep 13, 2007, at 14:15, joseph.h.dayney@rrd.com wrote:

> In getting SVN, TSVN, trac and CABIE to ALL integrate and speak a
> common tongue ... came upon the following. In SVN, TSVN and
> CABIE, the notation for linking to Tickets in trac (or other Bug
> Tracking Systems .... Bugzilla ... etc ) is [9] or [9,10,11]
> where 9 is a single Ticket in trac ... and 9,10,11 is a series of
> Tickets in trac
> This works great. There is a really nice Tortoise to SVN GUI Commit
> Hook that prompts User for a Ticket Number upon commit to put in
> the SVN Log in the Notation .... [9] .... "Bug ID or Issue
> Nmbr: [9]"
> Then when the SVN Log is pulled up ... User can simply click on the
> [9] link to open the corresponding trac Ticket. Works exactly the
> same way in CABIE ... "Defects fixed in this build: [9]."
> So I created a Wiki Page for our Application Releases ... which is
> derived from the SVN Log and the Revisions included ... which
> includes the Issue link to trac .... "Bug ID or Issue Nmbr: [9]"
> If User clicks on the Link in the trac Wiki Page ... the Link
> Notation in trac is for Changeset (Diff Compare). The Ticket
> notation is #9 or Ticket:9 (assume #9, #10, #11 or ticket:9,
> ticket:10, or ticket:11 for ... series)
> Its easy enough to write a simple sed to change the notation in the
> SVN LOG ... to work in trac ... but was curious why the [9] was
> not used instead of the #9 or ticket:9, to be consistent with the
> other tools. Maybe trac was already using that notation before
> TSVN ... ?

It's best not to cross-post to multiple lists. Rather, select one
place where you believe your question is on-topic and ask it there.
If you don't get a good response, ask elsewhere where the question is
on-topic. Your question is off-topic for the Subversion Development
list (since you're not contributing to the development of the base
Subversion software), the Subversion Users list (since your questions
are about features specific to Trac and/or TortoiseSVN, not features
in the base Subversion software) and the Subversion Announce list
(which is for announcements pertaining to Subversion). The Trac Users
or TortoiseSVN Users lists are fine places to ask the question, but
not both at the same time. See:


Regarding the Announce list: "Please DO NOT POST to this list unless
it's an announcement. (The list is moderated anyway, so your post
will not go through unless it's a legitimate announcement.)"

Regarding the Dev list: "Non-development questions should be posted
to 'users' instead; that includes build problems, configuration
issues, etc, as well as usage questions."

Regarding the Users list: "Please post all usage questions here. If
you're in doubt as to whether a post should go here or to 'dev', then
it should probably go here first -- people will suggest posting it to
'dev' if that's appropriate. Please DO NOT post TortoiseSVN questions
to this list: TortoiseSVN is a separate project with its own mailing

The notice about TortoiseSVN questions should be read to extend to
other software, like Trac, as well. Most of these other projects that
work with Subversion have their own lists where you can ask
questions. Many of us on the Subversion Users list, such as myself,
do not use TortoiseSVN or Trac and are thus ill-equipped to answer
your question, which is why it's best to ask questions about those
pieces of software on their own mailing lists, not the main
Subversion Users list.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 20 17:49:13 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.