> Here are some places to get you started on writing your proposal: > > http://libgit2.github.com/libgit2/index.html (the full API > documentation -- priceless) > http://libgit2.github.com/api.html (the usage guide, with examples) > https://github.com/libgit2 (the list of language bindings, so you can > see real-life usage samples) Hello again! First of all thanks a lot for the references. You have helped me a lot. > Also, I have to agree with Jeff once again: Start researching and > impress us with an awesome application that shows how are you planning > to solve the problem you are facing -- in this case writing a minimal > git client. > > Remember that the sooner your application gets on Melange, the more > feedback it will receive! I began implementing the minimal git client[1]. I have implemented the "git-mktag" command. For this I have modified the "mktag.c" file from the "builtin" directory in order to make it run with libgit2. Basically the input file verification code is the same with the original one. I have just extracted the sha1, the object type, the tag name, the tagger, the comment and created a tag with git_tag_create. I have also used the original "usage.c" and "git-compat-util.h" for error handling. Is there a problem if the git2 client will reuse non-gitcore code, such as string parsing code, parameter parsing code, etc? Can someone look on my code and give me some feedback? Just before ending the implementation of the mktag command I have started thinking that maybe there was no need to reimplement this command, as it can be considered that libgit2 already has this feature. Even if it is so I am not sorry I did this, because by reimplementig it I had the chance to get used with git code and with libgit2 API. --Alex [1] https://github.com/sutiialex/Git2 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html