A. The first is applied and the second is applied and it all works out fine... B. The first is not applied (since the second contains the changes as well), the second is, and all works out fine
C. The first is applied, the second mangles things up and so the second is rejected with a note to resubmit a patch against the head
D. Same as C only the committer unmangles it and figures it out by hand...
Generally A or B happen.
Basically patches are verified that they are either reasonable to apply with no accompanying unit test or have an accompanying unit test, are in good form, make sense,etc...
Then the unit tests are run and if they succeed...its committed...and the submitter is thanked graciously. Otherwise the patch is rejected and the committer is asked to resubmit but maybe first run the unit tests this time! ;-)
-Andy
Dennis Doubleday wrote:
I have a question as to the right way to deal with patches that I've
created but which haven't been applied yet. If I have the CVS head
checked out and a patch that I need in there in my tree but not applied
to CVS yet, what happens if I want to create a second patch? This is
theoretical, I don't need to submit a second patch right now, but if I
did...?
--
To unsubscribe, e-mail: <mailto:poi-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:poi-user-help@;jakarta.apache.org>
-- To unsubscribe, e-mail: <mailto:poi-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:poi-user-help@;jakarta.apache.org>
