Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BC2A3107C8 for ; Mon, 9 Sep 2013 17:54:09 +0000 (UTC) Received: (qmail 16907 invoked by uid 500); 9 Sep 2013 17:54:09 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 16877 invoked by uid 500); 9 Sep 2013 17:54:09 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 16869 invoked by uid 99); 9 Sep 2013 17:54:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Sep 2013 17:54:09 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Sep 2013 17:54:03 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=bBhqE033+mgBB7Wpve6j5VB/wdF79z5p4/qRqKLiX+Q=; b=o7tHovasMQW5Yke4X41Q4hg177zBUBf4vd4RNYotQE5MwOqECA2SzVeGyRQtBCZEqhPEmSB4aGupM3tyHM3dKMPjFK20y8KwxrRrDJ8P59wG1NS4C+TLe2f0QAImSVCJZxFk9xR9o/uJTJXtfYFXszNnEXuGlIrzLywdpqY5KSY=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-3.v29.ch3.sourceforge.com) by sfs-alluradaemon-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VJ5eg-0001w1-Cp for allura-dev@incubator.apache.org; Mon, 09 Sep 2013 17:53:42 +0000 Content-Type: multipart/related; boundary="===============6944986346876341196==" MIME-Version: 1.0 To: "[allura:tickets] " <6140@tickets.allura.p.re.sf.net> From: "Dave Brondsema" Reply-To: "[allura:tickets] " <6140@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #6140 Support trac commit/ticket syntax Message-ID:

Date: Mon, 09 Sep 2013 17:53:42 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============6944986346876341196== Content-Type: multipart/alternative; boundary="===============3822889649719157995==" MIME-Version: 1.0 --===============3822889649719157995== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit With [#6610] changing Trac import to use HTML as its basis, the cross-reference links will be handled nicely with no special parsing of them (they're already links). So this will just need to be applied to commit messages. See also [#6111] which is to have commit messages not be handled as full markdown, but just make their artifact references be links. --- ** [tickets:#6140] Support trac commit/ticket syntax** **Status:** open **Labels:** import trac **Created:** Thu Apr 18, 2013 09:30 PM UTC by Dave Brondsema **Last Updated:** Tue Aug 27, 2013 07:10 PM UTC **Owner:** nobody Tickets & wiki imported from trac [#4213] and [#6139] as well as SVN commits that have trac syntax for referencing tickets and svn revisions should still work in Allura. Examples: * `#123` for tickets (no brackets) * `r456` for svn revision * https://sourceforge.net/apps/trac/gfarm/changeset/8016 * A less frequent format: * `ticket:100` * `comment:13:ticket:408` * `source:gfarm_v2/trunk/server/gfmd/inode.c@6697#L3233` We can't change content during import since it's in SVN commit messages too. A regex should be easy to identify these. TBD: allow this simpler syntax all the time, or just for trac-imported content via some flag? --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============3822889649719157995== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

With [#6610] changing Trac import to use HTML as its basis, the cross-reference links will be handled nicely with no special parsing of them (they're already links).

So this will just need to be applied to commit messages. See also [#6111] which is to have commit messages not be handled as full markdown, but just make their artifact references be links.

[tickets:#6140] Support trac commit/ticket syntax

Status: open
Labels: import trac
Created: Thu Apr 18, 2013 09:30 PM UTC by Dave Brondsema
Last Updated: Tue Aug 27, 2013 07:10 PM UTC
Owner: nobody

Tickets & wiki imported from trac [#4213] and [#6139] as well as SVN commits that have trac syntax for referencing tickets and svn revisions should still work in Allura. Examples:

We can't change content during import since it's in SVN commit messages too.

A regex should be easy to identify these. TBD: allow this simpler syntax all the time, or just for trac-imported content via some flag?

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============3822889649719157995==-- --===============6944986346876341196==--