At 04:48 PM 9/13/95 +0100, you wrote:
>
>Now I'm confused. Are 1a and 1b two separate patches, or two versions of
>the same patch (I think the latter is what the names mean)?
Sorry, what I did was create 1a, and 1b which are BOTH needed to fix
a compiling error on Linux that appeared with patch 16_0.8.12. BOTH
patches are needed, they're two seperate files. I should have just named
it '1' and put both diffs in the same file.
>
>And, to repeat an earlier question, if a patch requires other patches,
>should it include all the patches it requires (i.e. diff -C3
>against the original code), or should it patch the patches (i.e. diff -C3
>against the original code+the required patches)?
From the last round-about I belive if a patch if for a patch it goes against
the next release not this one. So if you want to create a patch for my
patch it would go against the 0.8.14 source code.
>
>While we're on the subject of patch naming/voting, what happens if two
>alternates for the same patch get the same number of +1 votes?
>
Ahh... I think I know what you mean, but I don't have an answer.
<Aram>
--
Aram W. Mirzadeh, MIS Manager, Qosina Corporation
http://www.qosina.com/~awm/, awm@qosina.com
Apache httpd server team
http://www.apache.org