On Mon, 2007-03-19 at 08:01 +0100, Marco Costalba wrote: > I' have tried to do the list myself, but I found only viewers ;-) > among _currently_ tools I know of, and all the viewers allow loading > in background _now_ so will not be portable to libgit without main > surgery, read multi-thread (BTW none is currently multi-thread). I thought about configuration tools (gconf, kconfig, etc), that could then implement something similar to what the recovery system of WinXP does: they could store an history of the configuration state, and then recover a previous state if things go wrong. This would be incredibly useful for system administrators. Also, more generally, git can be used as a versioned storage system without direct link to source control. I'm thinking about ikiwiki for instance. More SCM-oriented, a cron script that manages a website by checkouting several repositories (one for the wiki module, another for the blog module, another for the forum, etc) using, say, the python bindi There are probably a zillion other possible uses. The common thing when exposing an API is that it ends up being used in a way nobody had thought of. So it's dangerous to say "it's useless" or "nobody will do it". You can be sure someone will, it's just a matter of time. - 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