Marek Zizlavsky wrote:
> > what's the problem in writing your idea as patch?
> 
> The problem is, that I've never write a patch, so I'll have to
> learn how it works at first and then I'll be able to participate to
> the community. Now I just don't have time for that learning...

We are happy to help! It is actually easy. :)

1. Install git
Available in most if not all Linux systems, as well as for Windows
(get MsysGit) and surely also Mac OS. Likely in BSD too.

2. Configure git
git config user.name "Marek Zizlavsky"
git config user.email marekz...@gmail.com

3. Grab the latest libssh2 source code
git clone git://git.stuge.se/libssh2.git

4. Make your suggested changes to the source files
cd libssh2/src
edit files

5. Review your changes
git diff

6. Save all your changes in your local git database
git commit -a

(This will ask you to write a commit message. Please write a summary
of your changes on the first line, and if you want to write more then
first add a blank line and continue the message after that.)

7. Create the patches (one is created for each commit you have made)
git format-patch origin

8. Email these patches as text/plain attachments to this list
If there are no complaints, they are committed to the official
repository.


In order to save time it is always smart to do what you did - come to
the list first and discuss a feature or a change, to find out what
the general opinion is about it. If you communicate early you can
save yourself time re-working the patches after community review.


> Yes please, write the patch for me, if you can. Thank you.

You will find that this doesn't always work so well. Feature requests
are great for when developers have free time - but a patch is always
worth more. :)


> And I'll have to get in touch with libssh2 source code at first of
> course...;-)

I think you already did that, to find that variable in the struct. So
you've really done all the work already. :)


//Peter
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel

Reply via email to