to be broken by an update, and to notify their maintainers as
a courtesy, eventually telling them what they are expected to update.
Cheers,
--
Julien Plissonneau Duquène
ure request), by explaining to them that
this will make the long-term maintenance of the documentation easier,
e.g. when features or bugfixes are backported from a newer version into
a stable version.
Thank you for working on this.
Cheers,
--
Julien Plissonneau Duquène
urce form if a tool is written for that, so I believe that it's
fine to proceed that way.
Cheers,
--
Julien Plissonneau Duquène
riate.
Cheers,
--
Julien Plissonneau Duquène
versioning scheme that
would allow to make it reproducible).
Cheers,
--
Julien Plissonneau Duquène
...@bugs.debian.org with a short
explanation, e.g.:
Closing this RFP: this package is already in sid.
Cheers,
--
Julien Plissonneau Duquène
chive which looks like not something anybody would ever want
to do intentionally
- comment in the bug report and either retitle it as something like
"document 7z a behaviour" or tag it as wontfix, and reduce its severity
to "minor"
- close the bug with the release that documents this behaviour of 7z a.
Cheers,
--
Julien Plissonneau Duquène
port.cgi?bug=1091675;msg=10
(look for signature.asc at the bottom)
--
Julien Plissonneau Duquène
8 matches
Mail list logo