2012/10/12 Charles Lepple <[email protected]>: > https://github.com/clepple/nut/pull/2#issuecomment-9356397 > > same comment from before still stands: > > [I took the liberty of replying on nut-upsdev - not many people are using > github yet since the NUT repository native format is still SVN.] > > Also, "pull requests" don't really make much sense when we are still > committing back to SVN, either. With git-svn, we can't do arbitrary merges - > we can only rebase and run "git svn dcommit", which flattens out the > repository history. Github assumes you are running a native Git repository, > so closing a pull request doesn't make it clear whether or not the code has > been merged. >
Agree, but it helps to track code to merge. >> @balooloo : I would however like to see some documentation. Strange that you >> missed that! >> The right place to insert this is 8.2 (after C/C++, before Python) > > In my mind, this is the biggest roadblock to merging. Developers need to know > that this library exists (News section of website, etc.) and need to know why > they might want this over the existing C API. Then, they need to know how to > use it. Much of the benefit of a wrapper library evaporates if a developer > has to basically read through the code to understand how to use it. > Agree too. I can write a little paragraph to talk about this lib (in C/C++ sub chapter) but I think writing man pages is not really efficient due to the API size (in term of function number). IMHO a doxygen like documentation is more relevant. I will work on that, but perhaps the merge can be done without this. > At the very least, the code in hazelnut can be cited as an example of how to > use libnutclient. > Why not, but this code will increase and, as it uses UI lib, it is not really easy to understand. I am working on a little C++ program using libnutclient which query upsd and dump results in csv file. This is probably a better example of what it can do and how to use it. > - a pkg-config support file That is commited. Regards, Emilien _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
