Message is undeliverable.
Reason: Unable to access cc:Mail Post office.
Please retry later.
Original text follows:
---------------------
Received: from sob.htdig.org [209.75.193.22] by nass.usda.gov (ccMail Link to SMTP
R8.30.00.7)
; Fri, 12 Nov 1999 20:16:10 -0500
Return-Path: <[EMAIL PROTECTED]>
Received: from sob.htdig.org (localhost [127.0.0.1])
by sob.htdig.org (Postfix) with SMTP
id E43C3A139; Fri, 12 Nov 1999 17:25:51 -0800 (PST)
From: Geoff Hutchison <[EMAIL PROTECTED]>
Errors-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Mime-Version: 1.0
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Date: Fri, 12 Nov 1999 19:11:01 -0600
Cc: [EMAIL PROTECTED]
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Subject: Re: [htdig3-dev] About HtDig Patch Sites
Sender: [EMAIL PROTECTED]
At 4:46 PM -0600 11/12/99, Gilles Detillieux wrote:
>it out to me last week. Until then, for the past couple months, I was
>using contrib/other for my own patches.
>
>Personally, I get the impression Joe's doing a pretty thorough job, as far
>as I can tell, so if we're going with just one, I'd say we go with his.
>It would be a good idea if we mirrored it on htdig.org, though.
Yes, Joe does a *very* comprehensive job, and on more than one
occaision, I've discovered a "long-lost" patch in his archive.
One suggestion I have is that
a) We clearly need a contrib/patches directory on htdig.org
b) We should designate "recommended" patches, like the "infamous bare
ampersand" problem Gilles mentioned.
So the way I see it, we should mirror Joe's archive wholesale in
contrib/patches *and* make a separate directory files/patches for
"recommended" patches to be integrated into new releases.
>That's always up to the discretion of the developers, but without a
>formalized process for this, patches do get forgotten. I've been
>pretty thorough about making sure my own fixes make it into 3.2,
>but I know I've let a lot of other patches slip through the cracks.
>Usually someone else gets them, but not always.
Yeah... I have a mail directory for that, but with the 3.2 release I
haven't been good about stuffing them in. It's also more complex than
the early 3.1.0bX releases when I was the only one writing to the
tree.
I don't know of a good way to do this. I've been trying to come up
with one as I realized I had less time this fall than I had hoped.
Loic had suggested using the bug-reporting system as a way of
flagging projects/tasks to be tackled and re-assigning them as
necessary. It's not a bad idea, but we'd need to make sure people
used it.
I'm obviously open to suggestions, but the only other suggestion I
have is that we go back to my folder approach where you either apply
the patches yourself or you make sure you send them to me (maybe with
a special subject to prevent it from getting lost?). I do care of any
loose threads I know of before I let something go out the door.
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
