Le Dim 7 Mai 2006 05:49, Anthony DeRobertis a écrit :
On Fri, May 05, 2006 at 09:35:16AM +0200, Pierre Habouzit wrote:
Could you please point me to an UNMERGED bug to see what it looks
like ? (an URL to the {status=closed ; resolution=merged} bug that
was reopen, as well as the bug in was
On Fri, May 05, 2006 at 09:35:16AM +0200, Pierre Habouzit wrote:
Could you please point me to an UNMERGED bug to see what it looks like ?
(an URL to the {status=closed ; resolution=merged} bug that was reopen,
as well as the bug in was merged into).
Le Ven 5 Mai 2006 05:49, Anthony DeRobertis a écrit :
On Wed, May 03, 2006 at 01:21:41PM +0200, Pierre Habouzit wrote:
* the forward canonization is vital for things like tracking
bugzilla's merges (it in fact rewrites a
$(uri)/show_bug.cgi?old_nnn into the $(uri)/show_bug.cgi?new_nnn)
On Wed, May 03, 2006 at 11:56:32AM +0200, Pierre Habouzit [EMAIL PROTECTED]
wrote:
This tool lists every BTS bug that is forwarded to a remote Bug
Tracker. If it knows how to get a Status and possibly a Resolution (if
the Status is a closing Status), it gets them, and:
* sets upstream,
On Wed, May 03, 2006 at 01:21:41PM +0200, Pierre Habouzit wrote:
* the forward canonization is vital for things like tracking bugzilla's
merges (it in fact rewrites a $(uri)/show_bug.cgi?old_nnn into the
$(uri)/show_bug.cgi?new_nnn)
Out of curiosity, how does it handle un-merges in
On Wed, May 03, 2006 at 11:56:32AM +0200, Pierre Habouzit wrote:
So basically to trig it, you just have to set the right forward status
for your bugs.
What is the right forward status? An URL for the upstream bug?
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email
Le Mer 3 Mai 2006 12:06, Steinar H. Gunderson a écrit :
On Wed, May 03, 2006 at 11:56:32AM +0200, Pierre Habouzit wrote:
So basically to trig it, you just have to set the right forward
status for your bugs.
What is the right forward status? An URL for the upstream bug?
Exactly. the
Le Mer 3 Mai 2006 11:56, Pierre Habouzit a écrit :
How to Help:
You can also help me to make the btslink.cfg more complete and
know about more bugzillas [7]
about that:
* private or mails to [EMAIL PROTECTED] are fine
* any bugzilla that is used for a project packaged in debian
On Wed, May 03, 2006 at 11:56:32AM +0200, Pierre Habouzit wrote:
Hi developers,
Like many of you may have noticed, a quite big mail was processed by
the BTS today [1]. This was generated by a new service I'm currently
developing, called bts-link.
This tool lists every BTS bug
Le Mer 3 Mai 2006 12:23, Alexander Sack a écrit :
On Wed, May 03, 2006 at 11:56:32AM +0200, Pierre Habouzit wrote:
Hi developers,
Like many of you may have noticed, a quite big mail was processed
by the BTS today [1]. This was generated by a new service I'm
currently developing,
On Wed, May 03, 2006 at 01:21:41PM +0200, Pierre Habouzit wrote:
btslink will *never* close or reopen bugs. So it's pretty harmless IMHO,
this won't resurect a RC bug for which you made a debian-only patch and
that is still not fixed upstream.
So just tell me if somethings looks illogical
Hi,
Re: Pierre Habouzit 2006-05-03 [EMAIL PROTECTED]
* as of tags, it only touches (like I explained) :
- upstream: ensure it's always set
- wontfix: try to guess if upstream tagged that bug wontfix, and
set/unset it accordingly
- fixed-upstream:
if
Le Mer 3 Mai 2006 14:02, Alexander Sack a écrit :
Anyway, I would have preferred to roll this out in a different
fashion:
1. release it as a package so all maintainers can use the tool if
they like.
I intended it like that at the begining. sadly, the tool uses a local
mirror of the
* Christoph Berg [EMAIL PROTECTED] [2006-05-03 14:28]:
Automatically setting the 'fixed-upstream' tag is certainly a very
nice idea that no one will object to.
Unfortunately, there are always corner cases. What if upstream marks
something as fixed, you get a Debian bug report that the bug is
* Martin Michlmayr ([EMAIL PROTECTED]) [060503 14:45]:
* Christoph Berg [EMAIL PROTECTED] [2006-05-03 14:28]:
Automatically setting the 'fixed-upstream' tag is certainly a very
nice idea that no one will object to.
Unfortunately, there are always corner cases. What if upstream marks
Le Mer 3 Mai 2006 14:28, Christoph Berg a écrit :
Automatically setting the 'fixed-upstream' tag is certainly a very
nice idea that no one will object to.
For 'upstream', I don't really see a benefit of setting it since the
bug is already marked as forwarded. I would just leave it alone not
Le Mer 3 Mai 2006 14:44, Martin Michlmayr a écrit :
* Christoph Berg [EMAIL PROTECTED] [2006-05-03 14:28]:
Automatically setting the 'fixed-upstream' tag is certainly a very
nice idea that no one will object to.
Unfortunately, there are always corner cases. What if upstream marks
On Wed, May 03, 2006 at 11:56:32AM +0200, Pierre Habouzit wrote:
It currently only support bugzilla (which would still help kde, gnome,
X.org, linux kernel, samba, mozilla, gcc Maintainers to cite only them),
but is written so that adding new backend is not a difficult task.
Could you please
Le Mer 3 Mai 2006 17:54, Stefano Zacchiroli a écrit :
On Wed, May 03, 2006 at 11:56:32AM +0200, Pierre Habouzit wrote:
It currently only support bugzilla (which would still help kde,
gnome, X.org, linux kernel, samba, mozilla, gcc Maintainers to cite
only them), but is written so that
* Pierre Habouzit [EMAIL PROTECTED] [2006-05-03 15:49]:
IMHO, in his case, he should remove the forward, tag the bug
upstream, and mention in the bug history that this is related to the
upstream bug foo. set the forwarded state of a bug does not makes
sense to me, if you dont adhere to how
* Pierre Habouzit [EMAIL PROTECTED] [2006-05-03 16:30]:
after more pondering, what really miss for me, is a BTS
closed-upstream tag, meaning that the bug is closed on the remote
BTS, but not necessarily fixed.
I don't think this distinction is helpful. Also, it's exactly
opposite to what it
Le Mer 3 Mai 2006 18:55, Martin Michlmayr a écrit :
* Pierre Habouzit [EMAIL PROTECTED] [2006-05-03 15:49]:
IMHO, in his case, he should remove the forward, tag the bug
upstream, and mention in the bug history that this is related to
the upstream bug foo. set the forwarded state of a bug
22 matches
Mail list logo
