Gnus development mailing list
 help / color / mirror / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: A New Year's Resolution
Date: 04 Jan 2000 07:35:39 -0500	[thread overview]
Message-ID: <oqr9fyrp44.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: wjhardaker@ucdavis.edu's message of "03 Jan 2000 10:43:36 -0800"

wjhardaker@ucdavis.edu writes:

> Lars> Is there any point in responding to mail that more than 4 months old?

Hmph!  4 months is really nothing... :-) :-(

When I got `tar' maintenance (which I do not have anymore :-), `tar'
maintenance has already been put on hold for quite a long while.  I received
with it a huge backlog of accumulated problems, thousands of them.  I read in
all these reports a lot of frustration from users having had the impression
of writing into a black hole.  So, I made a point to reply to every message
while I was processing it, _however_ old it was.  Then, John Gilmore, the
original `tar' author, sent me his own collection of accumulated messages,
which was another big lot, and generally much older.  I merged everything.

I surely solved many thousands of messages, and just to keep the rope tight,
also received thousands of new messages.  Many single messages did require
a great deal of work.  `tar' is by far the most demanding package I ever
took care of, if you consider all the overhead it takes to do a proper job.
It was impossible for anyone-not-being-Lars to reply timely to everything.

Yet, when one installs a patch in 1998 for a problem first reported in 1989,
one feels strange while acknowledging the contribution to the submitter! :-)
Even then, my opinion is that we should never dismiss a user report, and
that even if some problems solve "themselves" over time, some just do not.

P.S. - My main hope is that `tar' is much more _maintainable_ now that it
originally was, the job should be more pleasurable to the new maintainer.

-- 
François Pinard   http://www.iro.umontreal.ca/~pinard





  parent reply	other threads:[~2000-01-04 12:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-02  6:11 Lars Magne Ingebrigtsen
2000-01-03 18:43 ` wjhardaker
2000-01-03 19:34   ` William M. Perry
2000-01-03 22:31     ` Russ Allbery
2000-01-03 22:37       ` Laura Conrad
2000-01-03 23:25         ` William M. Perry
2000-01-03 23:28           ` Laura Conrad
2000-01-03 23:26         ` Russ Allbery
2000-01-04  8:29       ` Kai Großjohann
2000-01-04  9:22         ` Russ Allbery
2000-01-04 11:11           ` Kai Großjohann
2000-01-04 14:56             ` Henrik Holm
2000-01-04 14:59               ` Henrik Holm
2000-01-04 12:02           ` Simon Josefsson
2000-01-04 14:26     ` Per Abrahamsen
2000-04-21 14:22       ` Lars Magne Ingebrigtsen
2000-01-05 19:05     ` wjhardaker
2000-01-04 12:35   ` François Pinard [this message]
2000-01-04 14:53     ` luis fernandes
2000-01-03 18:51 ` wjhardaker
2000-01-04  5:48   ` Amos Gouaux
2000-01-05 18:59     ` wjhardaker
2000-01-10  5:58     ` Matt Simmons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=oqr9fyrp44.fsf@titan.progiciels-bpi.ca \
    --to=pinard@iro.umontreal.ca \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).