Subject: Re: Bugzilla bug tracking database for 2.5 now available.
To: Larry McVoy <lm@bitmover.com>
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org,
       linux-kernel-owner@vger.kernel.org, mbligh@aracnet.com
Message-ID: <OF13B0B9E1.574AFCAA-ON85256C72.00595C26@pok.ibm.com>
From: "Khoa Huynh" <khoa@us.ibm.com>
Date: Fri, 15 Nov 2002 10:23:19 -0600
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1186
Lines: 31


>This may or may not help but it seems relevant.  BK has uniq names for
>each changeset, we're fixing BK/Web so you can use the uniq names instead
>of the revs (which change out from under you).
>
>So it should be possible to link the bug report with a changeset in Linus'
>tree if you want.
>
>It's worth pointing out that if you can see the bug in a particular
version
>of Linus' tree then *everyone* can see it by getting a copy of the tree
>as of that cset.  BK guarentees that if you clone -r<rev> then you'll see
>exactly what anyone else saw as of that cset.

Yes, this is great!  We can create a separate field in the bug reports to
contain this unique names, so we can reference the cset directly from
the bug reports.  This allows us to link bug reports to csets -- great!

What format will these unique names be in?  If we put them in the bug
reports,
can we click on them (as URLs) and get to the csets directly?
Thanks.

Khoa


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/