"Kyle J. McKay" <mack...@gmail.com> writes:

> However, upon further consideration (I noticed that the preparatory
> patch and v4 of the textual matching patch made their way into pu),

Do not read too much into being in 'pu'.  They are there primarily
so that I won't forget what is in-flight and can be replaced or

> perhaps it would be more convenient for you if I re-released the
> following patch series:

Sorry, but I do not understand.  What do you mean by having these
three patch series?  Are they "There are three possibilities, pick
one and discard the other two"?  If so, then as the maintainer, I
personally would not care ;-), as they would be commented upon, and
I won't pick any of them up until there is one list favorite.

If "These build on top of each other in this order", then it is
easier for me to manage if they were in a single series.

If f1ff763a (http.c: fix parsing of http.sslCertPasswordProtected
variable, 2013-07-12) is already solid and need no further tweaking,
it would be wise not to include the patch in any of your reroll in
any case.  Instead, just build your series on top of that commit,
and make it clear that the series is meant to apply on top of that
commit in the cover letter [0/n] of the series, or after "---" line
of the first patch [1/n] in the series.

As to allowing GIT_SSL_CERT_PASSWORD_PROTECTED=no, I agree that it
does not belong to the http.*.<var> configuration series, so making
it an independent patch, perhaps on top of f1ff763a, would make
sense.  If the other patches have any textual dependency, you can
make it [1/n] of your series and we can treat it just like f1ff763a,
that is, make sure it is solid regardless of the rest of the series,
and make it advance before the remainder of the series, so that we
can still replace http.*.<var> implementation on top of these two

> [PATCH v5]: config: support http.<url>.* settings - (1) textual matching
> * contains 0001 the same preparatory http.sslCertPasswordProtected
> * contains 0002 the same v5 textual matching http.<url>.* patch
> [PATCH v2]: config: support http.<url>.* settings - (2) url
> normalization
> * contains 0001 url normalization matching with feedback updates
> * contains 0002 url normalization test
> [PATCH v1]: config: support http.<url>.* settings - (3) any user
> matching
> * contains 0001 a new patch that extends (2) to include any user
> matching
> And drop the GIT_SSL_CERT_PASSWORD_PROTECTED patch as while it's
> logically related to the http.sslCertPasswordProtected patch it's not
> logistically related since independent areas of the file are touched
> and it could be successfully applied before or after the other
> patches.  It can go together with any forthcoming enable-only fix for
> GIT_SSL_CERT_PASSWORD_PROTECTED and other such environment variables
> or just be dropped entirely.
> I do not, however, wish to create any additional maintainer work, so
> wanted to check with you before sending out any of the reissues.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to