{"thread":{"id":"26970","subject":"Re: git: ideas and libgit2","startedAt":"2011-04-03T01:01:05Z","lastAt":"2011-04-03T01:01:05Z","messageCount":1,"participants":["Jonathan Nieder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"164971","messageId":"20110403010040.GA25840@elie","threadId":"26970","inReplyTo":"AANLkTimry9cvwQZ1bJYeUK6xafahtw-FgOWnDggfLdxJ@mail.gmail.com","subject":"Re: git: ideas and libgit2","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-04-03T01:01:05Z","receivedAt":"2011-04-03T01:01:05Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"(cc-ing the git list; hoping that's okay.)\nHi Thiago,\n\nThiago Farina wrote:\n\n> Would you help me to find some ideas to work on git? I'd also be\n> interested in working in some API related to libgit2.\n\nI'm probably not a good bet for that, since I'm not familiar with\nlibgit2 at all.  You'd probably want to contact the libgit2 list at\n<libgit2@librelist.org>.\n\nBecause of Google's summer program there's a list of potential\nprojects at <https://git.wiki.kernel.org/index.php/SoC2011Ideas>.\nSome people were mentioning the possibility of keeping a list like\nthis year-round, to give people something to hack on.\n\nI can help find a project in the field of merge, remote helpers,\ndocumentation processing, or startup procedure (repository discovery\nand option parsing).  Or you can steal a project from me, if you'd\nlike.  Here's a few:\n\n - glibc: <http://sourceware.org/bugzilla/show_bug.cgi?id=6530>.\n   This is desperately needed before translated output from the\n   git cli becomes possible.\n\n - unifdef: split into coroutines following the stages of\n   preprocessing described by the C standard, so it can handle more\n   real-life preprocessor conditionals.  This should help with\n   understanding the #ifdef-ed mess that is glibc's printf (see\n   above).\n\n - various git commands: support --patience, for patience diff.\n   Make a simple test script to demonstrate that it's turned on.\n   Especially nice would be \"git add -p\".\n   http://bugs.debian.org/522361\n\n - daemon: add some tests (using daemon --inetd, presumably).\n   Let the client know when the repository is inaccessible:\n   http://thread.gmane.org/gmane.comp.version-control.git/145456/focus=145573\n\n - daemon: add an option to stop tolerating inability to listen\n   on one of the supplied interfaces.  Make a sysvinit / systemd /\n   runit / whatever script describing best practices for running a\n   persistent git daemon for contrib.\n\n - git test suite: find the remaining missing \"&&\"-s, fix them, and\n   make future tests without them automatically fail.\n   http://thread.gmane.org/gmane.comp.version-control.git/157903/focus=158265\n\n - scripts: use \"set -u\" in git-sh-setup, and fix the errors that\n   result.  Some of the fixes won't be suitable for mainline: e.g.\n   use of GIT_ variables would have to change to\n\n\tif test \"${GIT_FOO:+set}\"\n\tthen\n\t\t... use GIT_ variable ...\n\tfi\n\n   to suppress the error, but I doubt mainline git wants it.  Other\n   fixes (protecting against the environment by initializing local\n   variables to be empty) would be very much suitable for mainline.\n\n - contrib: make a Makefile so the invoker can install all the crazy\n   contributed goodies at once if she wants to.\n\n - look for interesting (possibly old) patch series on the list\n   (like the whole-directory-rename series!) and nudge them forward.\n\nHope that helps,\nJonathan\n"}]}