On Thu, Dec 08, 2005 at 07:04:10AM +0100, Christian Perrier wrote:
...as announced 3 weeks ago.
In this -done message (as well as a few others), I forgot adding the
Version pseudo-header which makes the bug unproperly tracked by
Version tracking.
What would be the best way to do this
What would be the best way to do this properly. Is there somethign I
can do *after* closing the bug except reopening it and re-closing it?
Nope, reopen close is exactly the recommended approach. This can be done
to [EMAIL PROTECTED] directly, no need to use the -done address again.
OK,
On Thu, Dec 08, 2005 at 06:06:51PM +0100, Christian Perrier wrote:
What would be the best way to do this properly. Is there somethign I
can do *after* closing the bug except reopening it and re-closing it?
Nope, reopen close is exactly the recommended approach. This can be done
to
reopen 237390
close 237390 samba 3.0.14a-3
thanks
OK, that one should be right, thanks Steve for being my teacher.
Note to self: send a BR to the various docs which talk about close
and just say it is obsolete without giving the useful hints..:-)
--
To UNSUBSCRIBE, email to [EMAIL
Quoting Debian Bug Tracking System ([EMAIL PROTECTED]):
Processing commands for [EMAIL PROTECTED]:
close 237390 3.0.14a-3
Bug#237390: [TO CLOSE 20051118] Samba printing problem
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version
...as announced 3 weeks ago.
In this -done message (as well as a few others), I forgot adding the
Version pseudo-header which makes the bug unproperly tracked by
Version tracking.
What would be the best way to do this properly. Is there somethign I
can do *after* closing the bug except
6 matches
Mail list logo
