Lines Matching refs:to
2 # Developer information for contributing to libcoap #
9 Any contributions have to be made dual licensed under the terms of the
23 Please refer also to the libcoap website for additional information
39 want to discuss some patches, please write it to the mailing list. Please
40 avoid personal mailings to the maintainer (or some other contributor) if
42 You can subscribe to the list here:
57 To start any contributing you first have to clone the git tree from the main
65 development branch! To do so you have to first checkout the 'develop' branch
80 At some point you will have to generate patches to post them on the mailing
81 list (and/or push your changes into your public Git tree). It's a good idea to
85 To be able to send a patch series you will now create the series itself as
90 patches within a defined directory. Also, while create the patches, tell git to
99 your patches to libcoap-developers@lists.sourceforge.net
101 git send-email ../patches4libcoap/* --to=libcoap-developers@lists.sourceforge.net
111 take a look into existing files and adopt the needed changes to your new
116 * For better reading the indentation is set to 2 characters as spaces, this
119 It's appropriate to set up a modline like this one at first line within
144 * A useful source code documentation is mandatory. Mostly to be done within the
149 change existing functions. The doxygen documentation has to be done in the
151 @-syntax for doxygen commands (akin to javadoc).
157 always provide a wrapper for the old call to let the library be backward
165 Use the possibility to write a good explanation why your patch/commit is
168 way. Don't use something to generic like "bugfix commit".
170 * A patch/commit or a series of patches/commits have to ensure that the
171 whole project is able to build up every thing, in short: Do not break
177 typically your patch is to big for one single commit.
180 this your commit message helps to find thematic other changes. If you have
181 to search and find something with 'git log | grep [foo]' you will see why
188 6. Where to start contributing?
190 There are various things you could starting on to contribute, the best
193 from there or point the maintainer to add other things here too.
206 write to the mailing list explained in section 2.
212 Unfortunately there is no good user guide on how to use the libcoap in
214 programming person available. You want to write up something?