Hi Steve,

2012/6/8 Steve Holme <steve_holme_at_hotmail.com>:
> Hi Marc,
>
>> Okay, I think the best way would be to base your work on my rebased
>>  branch which still holds the whole development history:
>> https://github.com/mback2k/curl/tree/schannel-rebase-00fddba672
>
> There's still some areas of git that I'm not too familiar with or workflow
> that are different to the other version control packages I've used but I've
> done the following from TortoiseGIT:

I would like to recommend "Git for Windows" instead of TortoiseGIT,
because the latter hides a lot of git's power functionality. ;-)
http://msysgit.github.com/

> * Cloned the repository from https://github.com/mback2k/curl.git
> * Switched to the schannel-rebase-00fddba672 branch

That's a way to do it. But if you want to push to your own repo
instead of needing to generate e-mail patches, you could have created
a fork on github.com.
Anyway, you can just send your commits as a patch to the mailinglist.

> Will I have direct commit / push access to that branch or should I be
> working differently?

Yes, you will have commit access to your local clone, but you won't be
able to push to my personal fork on github.com.
Please take a look at this guide: https://help.github.com/articles/fork-a-repo

A better approach would to fork Daniel's repo and then pull my changes into it.

> I've just added support for APOP in a local branch here, which I hope to
> push over the weekend and once that is out of the way / whilst I wait for
> the autobuilds to run I will hopefully be able to re do my version info
> changes into your branch.

Cool!

Best regards,
Marc

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-06-08