Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: [PATCH v4] setopt: make curl_easy_vsetopt public
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Drew DeVault via curl-library <curl-library_at_lists.haxx.se>
Date: Tue, 29 Mar 2022 13:30:34 +0200
I don't think the curl mailing list is the right place to discuss this,
but I will at least answer some of your questions.
On Tue Mar 29, 2022 at 1:11 PM CEST, Timothe Litt via curl-library wrote:
> There are better ways to make your point. I've found that the best way
> to contribute to a project is to use whatever mechanism it provides, not
> to demand special treatment.
I am not demanding special treatment. Contributions via email are
accepted per the cURL developer documentation. I just used one of the
options which was available to me according to my preferences. If this
ran into problems with the process, the process should be improved. If
cURL indeed does not wish to receive changes via email, the
documentation should be updated. Either way, I've done nothing to merit
the acusatory tone of your email.
> Yours is the only material contribution to curl that I've seen done via
> e-mail. And it's not a particularly big change.
Prior to moving to GitHub, many curl patches were submitted via email.
curl is much older than GitHub, after all. The state of affairs prior to
the move sufficed for almost 20 years.
> You're not avoiding the use of github - all you're doing is using it
> indirectly - and in the process, consuming the time of its primary
> developer as an intermediary.
It's quite easy to apply my patch via email -- it's not necessary to
route it through a GitHub pull request at all. It's also possible to add
tooling like CI to mailing lists, much like it was added to the GitHub
repository. These are indeed good areas for improvement.
Date: Tue, 29 Mar 2022 13:30:34 +0200
I don't think the curl mailing list is the right place to discuss this,
but I will at least answer some of your questions.
On Tue Mar 29, 2022 at 1:11 PM CEST, Timothe Litt via curl-library wrote:
> There are better ways to make your point. I've found that the best way
> to contribute to a project is to use whatever mechanism it provides, not
> to demand special treatment.
I am not demanding special treatment. Contributions via email are
accepted per the cURL developer documentation. I just used one of the
options which was available to me according to my preferences. If this
ran into problems with the process, the process should be improved. If
cURL indeed does not wish to receive changes via email, the
documentation should be updated. Either way, I've done nothing to merit
the acusatory tone of your email.
> Yours is the only material contribution to curl that I've seen done via
> e-mail. And it's not a particularly big change.
Prior to moving to GitHub, many curl patches were submitted via email.
curl is much older than GitHub, after all. The state of affairs prior to
the move sufficed for almost 20 years.
> You're not avoiding the use of github - all you're doing is using it
> indirectly - and in the process, consuming the time of its primary
> developer as an intermediary.
It's quite easy to apply my patch via email -- it's not necessary to
route it through a GitHub pull request at all. It's also possible to add
tooling like CI to mailing lists, much like it was added to the GitHub
repository. These are indeed good areas for improvement.
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-03-29