Your message dated Sat, 17 Mar 2007 17:31:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line FW: bug wmaker?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: exim4
Version: 4.24-3
Severity: important
this bug is in response to several bug reports which i have raised
regarding exim4, which are all to do with improving exim4. each and
every such bug has been treated with derision.
READ THIS ARTICLE:
http://mako.cc/writing/to_fork_or_not_to_fork.html
excert from http://advogato.org/person/lkcl/diary.html?start=373
and this, from the summary - my favourite:
It's becoming increasingly difficult to reproduce these large
projects. While reproducing entire project is impossible for small
groups of hackers, it is often not even possible for small groups
to even track and maintain a fork of a large project over time.
it emphasises the RESPONSIBILITY and the DUTY that free software
developers have. we are GUARDIANS OF KNOWLEDGE - for the WORLD.
if you cannot accept that responsibility, to provide all things to all
people, **** OFF AND GIVE IT TO SOMEONE WHO CAN.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages exim4 depends on:
ii exim4-base 4.24-3 EXperimental Internal Mailer -- a
ii exim4-daemon-light 4.24-3 Lightweight version of the Exim (v
exim4 recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
> In my opinion, this bug should be closed, [..]
Yes, it should be closes; I don't see any bug report nor a reason for
hijacking.
Yours sincerely,
Alexander
--- End Message ---
