On Tue, Aug 16, 2005 at 07:47:01AM +0200, Mike Hommey wrote:
On Mon, Aug 15, 2005 at 03:41:43PM -0700, Steve Langasek [EMAIL PROTECTED]
wrote:
On Sun, Aug 14, 2005 at 02:00:04PM +0200, Mike Hommey wrote:
On Mon, Jul 18, 2005 at 12:06:29PM +0100, Colin Watson [EMAIL
PROTECTED] wrote:
On Sun, Aug 14, 2005 at 02:00:04PM +0200, Mike Hommey wrote:
On Mon, Jul 18, 2005 at 12:06:29PM +0100, Colin Watson [EMAIL PROTECTED]
wrote:
(...)
The 'reopen' command takes an optional submitter argument, so it was
difficult to get a version in here unambiguously. Instead, we've
On Mon, Aug 15, 2005 at 03:41:43PM -0700, Steve Langasek [EMAIL PROTECTED]
wrote:
On Sun, Aug 14, 2005 at 02:00:04PM +0200, Mike Hommey wrote:
On Mon, Jul 18, 2005 at 12:06:29PM +0100, Colin Watson [EMAIL PROTECTED]
wrote:
(...)
The 'reopen' command takes an optional submitter
- Forwarded message from Mike Hommey [EMAIL PROTECTED] -
From: Mike Hommey [EMAIL PROTECTED]
Subject: Re: BTS version tracking
To: Colin Watson [EMAIL PROTECTED], [EMAIL PROTECTED]
I'm really dumb today, I managed
On Wed, Jul 20, 2005 at 01:45:03PM +0100, Colin Watson wrote:
On Tue, Jul 19, 2005 at 10:34:23PM -0700, Brian Nelson wrote:
What if the maintainer uploads a version, say 1.3-2 (which is still the
most recent version), which supposedly fixes bug 1234567. However, I
test it and find that
Le Lun 18 Juillet 2005 23:36, Matthew Palmer a écrit :
On Mon, Jul 18, 2005 at 12:06:29PM +0100, Colin Watson wrote:
A frequently requested feature for the bug tracking system in
recent years has been the ability to track which bugs apply to
which distributions, so that, eg, maintainers and
On Tue, Jul 19, 2005 at 10:34:23PM -0700, Brian Nelson wrote:
Colin Watson [EMAIL PROTECTED] writes:
The 'reopen' command takes an optional submitter argument, so it was
difficult to get a version in here unambiguously. Instead, we've
introduced a new 'found' command, which says I've found
On Mon, Jul 18, 2005 at 10:28:06PM +0200, Andreas Barth wrote:
* Colin Watson ([EMAIL PROTECTED]) [050718 17:21]:
The BTS records that bug #NN was fixed in 1.1-sarge1 and 1.3, and
let's say the bug was found in version 1.1. Since it has the changelogs
(it gets these from ftp-master), it
On Mon, Jul 18, 2005 at 12:06:29PM +0100, Colin Watson wrote:
A frequently requested feature for the bug tracking system in recent years
has been the ability to track which bugs apply to which distributions,
so that, eg, maintainers and others can tell which bugs that have been
fixed in
Colin == Colin Watson [EMAIL PROTECTED] writes:
Colin A frequently requested feature for the bug tracking system
Colin in recent years has been the ability to track which bugs
Colin apply to which distributions, so that, eg, maintainers and
Colin others can tell which bugs that
Colin Watson [EMAIL PROTECTED] writes:
[...]
The 'reopen' command takes an optional submitter argument, so it was
difficult to get a version in here unambiguously. Instead, we've
introduced a new 'found' command, which says I've found the bug in this
version of the package. You can use this
On Mon, Jul 18, 2005 at 12:06:29PM +0100, Colin Watson wrote:
A number of changes have been made to [EMAIL PROTECTED] [1] to
support this. Firstly, the 'close' and 'reassign' commands now take
extra version arguments, as follows:
close 1234567 1.1
reassign 1234567 example-package 2.0-1
On Mon, Jul 18, 2005 at 08:35:45AM -0600, Rob Sims wrote:
On Mon, Jul 18, 2005 at 12:06:29PM +0100, Colin Watson wrote:
A number of changes have been made to [EMAIL PROTECTED] [1] to
support this. Firstly, the 'close' and 'reassign' commands now take
extra version arguments, as follows:
* Colin Watson ([EMAIL PROTECTED]) [050718 17:21]:
The BTS records that bug #NN was fixed in 1.1-sarge1 and 1.3, and
let's say the bug was found in version 1.1. Since it has the changelogs
(it gets these from ftp-master), it can build up a tree of which package
versions are based on which
14 matches
Mail list logo
