Hi

On 14 April 2012 08:54, Marc Hoersken <info_at_marc-hoersken.de> wrote:
[...]
> Guenter recommended attaching a patch itself and this is what I do
> now, so that you can test the current version. But once it is going to
> be merged into libcurl, I would really like to see my development
> branch on github, including its commit history, being merged into the
> main git repository. I read that this is not you normal workflow for
> patches, but please consider the useful information in the commit
> history of such a big patch.
[...]

You can still provide the full commit history as patches by using "git
format-patch".

I haven't looked at the patch set, but if you have initial
modifications and then later updates to the same things it might make
sense to squash some of your commits to avoid unnecessary noise in the
commit history before it is committed to the curl repository. I'm
sure someone with the ability to commit your work will let you know if
that's necessary, though. :)

-- 
Michael Wood <esiotrot_at_gmail.com>
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html