Re: RFC round 3: DEP-3: Patch Tagging Guidelines

To: debian-devel@lists.debian.org
Subject: Re: RFC round 3: DEP-3: Patch Tagging Guidelines
From: Jakub Wilk <ubanus@users.sf.net>
Date: Sat, 4 Jul 2009 09:01:17 +0200
Message-id: <[🔎] 20090704070117.GB4399@cavendish.icomputing.pl>
In-reply-to: <[🔎] d1b732a70907031803l38eaf043s1091177065363465@mail.gmail.com>
References: <20090629205353.GC15110@rivendell> <[🔎] 4A4E4FC0.4020204@jameswestby.net> <[🔎] 20090704005828.GB1988@belanna.comodo.priv.at> <[🔎] d1b732a70907031803l38eaf043s1091177065363465@mail.gmail.com>

* Jonathan Yu <jonathan.i.yu@gmail.com>, 2009-07-03, 21:03:

Maybe an idea is to have a format like:

Bug: #123456 (assumes Debian BTS)
Bug: BTS#123456 (same as above, but explicit)
Bug: RT#123456 (to point to the CPAN Request Tracker)

So, you are expecting that someone who reviews a patch would known howto convert bug numbers to URLs for *all* these trackers?


--
Jakub Wilk

Reply to:

Follow-Ups:
- Re: RFC round 3: DEP-3: Patch Tagging Guidelines
  - From: Jonathan Yu <jonathan.i.yu@gmail.com>

References:
- Re: RFC round 3: DEP-3: Patch Tagging Guidelines
  - From: James Westby <jw+debian@jameswestby.net>
- Re: RFC round 3: DEP-3: Patch Tagging Guidelines
  - From: gregor herrmann <gregoa@debian.org>
- Re: RFC round 3: DEP-3: Patch Tagging Guidelines
  - From: Jonathan Yu <jonathan.i.yu@gmail.com>

Prev by Date: Re: [Debconf-discuss] GPG keysigning?
Next by Date: Re: ia32-libs{-tools}, multiarch, squeeze
Previous by thread: Re: RFC round 3: DEP-3: Patch Tagging Guidelines
Next by thread: Re: RFC round 3: DEP-3: Patch Tagging Guidelines
Index(es):
- Date
- Thread