reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To UNSUBSCRIBE,
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To UNSUBSCRIBE,
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To UNSUBSCRIBE,
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again...closing
without explanation is *not* cleanup.
--
To UNSUBSCRIBE,
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
reopen 386363
severity 386363 minor
retitle 386363 important priority for non-necessary tool
thanks
The wontfix tag should be reserved for open bugs to indicate that they
will never be closed, so you shouldn't close a bug in addition to
tagging it wontfix.
Debian Policy describes priority
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
reopen 386363
thanks
From http://www.debian.org/Bugs/Developer.en.html#closing :
The message body needs to contain an explanation of how the bug was fixed.
Thank you for including that if you wish to close the bug again.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
19 matches
Mail list logo
