httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Sutton <>
Subject Re: [POLL] apachen/patches directory
Date Mon, 12 Jan 1998 09:43:55 GMT
On Sun, 11 Jan 1998, Rodent of Unusual Size wrote:
> I'm calling the question on the putting-patches-into-a-directory
> issue.  The specific details (such as where it should be, what it
> should be called, whether "Subject: [PATCH]" messages should
> be auto-committed there, and whether CVS messages about commits
> to that directory should be burnt-before-sent, among others) can be
> worked out later.

What's "burnt-before-sent" mean? Commit messages to the patches directory
are surely vital so that the committed can explain the purpose and need
for their patch? If not how do we match up the patch against the
discussion on new-httpd, unless the patcher manually sends their patch to
the list as well, with the description?

> So.. the question is, shall a directory be created somewhere in
> the source tree so patches can be made available through cvs update
> rather than requiring separate mail to new-httpd?  Votes, please.

0. I'm not convinced that this is necessary. But provided that the commit
message is used to contain the full description of the patch and why it is
necessary, and that the commits go to new-httpd, then I'm not against it
either. I like the optionality of the question above -- presumably people
can still mail thie patches to new-httpd just like now? 


View raw message