Lines Matching refs:on
18 The used VCS for libcoap is Git, the main repository is living on GitHub.
19 You can clone (or fork directly on GitHub) on the repository site:
27 The build environment is grounded on the classical autotools, the GNU GCC and
37 on Sourceforge.
46 The archive of the list can be found on:
55 holding the point releases, all the development process is going on in the
58 repository on GitHub:
62 4. Working on the source
64 As one golden rule you should work on improvements within *your* own local
66 as local branch and then start on top on this branch your own branch. So
80 At some point you will have to generate patches to post them on the mailing
82 post your patch series on the mailing list so other contributors will see your
117 is depended on the often used nested functions like 'if-else'. Don't use
159 Please discuss needed changes on the mailing list.
186 address.[hc]: make coap_address_equals() not inline on POSIX
190 There are various things you could starting on to contribute, the best
196 We are always lacking on a better documentation on the source code, so
198 Also a good documentation on the usage of the libcoap and the example
199 binaries is always improvable. So we appreciate any help on this.
204 quite more than simple examples on a system. There are man pages for these
207 Maybe you can write up some good HowTo's on the usage for these binaries. A man
212 Unfortunately there is no good user guide on how to use the libcoap in