Subject: Re: [htdig3-dev] About HtDig Patch Sites
From: Joe R. Jah (firstname.lastname@example.org)
Date: Sun Nov 14 1999 - 22:25:22 PST
On Fri, 12 Nov 1999, Joe R. Jah wrote:
> Date: Fri, 12 Nov 1999 16:38:49 -0800 (PST)
> From: "Joe R. Jah" <email@example.com>
> To: firstname.lastname@example.org
> Cc: email@example.com
> Subject: Re: [htdig3-dev] About HtDig Patch Sites
> > I guess we'd also want a mechanism for overriding or replacing patches
> > with corrected versions. I've submitted patches from time to time, only
> > to have someone point out a correction. I've also found some posted
> > patches that were in need of corrections (e.g. a patch that tested a
> > boolean parameter as a string, comparing it against "0", rather than
> > using config.Boolean()). When a corrected patch is submitted, the
> > defective one should be taken off - how will this be specified?
> I believe in history and archives; I think it is a good idea not to
> destroy any document because they may turn out to be helpful to someone
> in some way. That's why I use a numbering scheme to signify chronology
> patches; i.e.
> There must be a better way of doing that; I am open to suggestions.
I created an 0ld directory under 3.1.3 patch directory, and moved the two
old/redundant patches in there. When you submit a corrected patch I will
move the defective one to the 0ld directory.
-- _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ _-\<,_ _/ _/ _/_/_/ _/ _/ ......(_)/ (_) _/_/ oe _/ _/. _/_/ ah firstname.lastname@example.org
------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to email@example.com containing the single word "unsubscribe" in the SUBJECT of the message.
This archive was generated by hypermail 2b25 : Sun Nov 14 1999 - 22:36:13 PST