On 0, Marco Costalba <mcostalba@xxxxxxxxx> wrote: > > I understand the main reason, as per any GPL project, is having fun > and good time coding and exchanging ideas with peers, but I really > lack time and I am now moving to different interests. So, thank you > very much, but I think I'll stick with qgit. > > Best > Marco One thing, though, that I think everyone can agree on is that getting a common lib for git guis is really step #2. Step #1 would be to work towards libgit, since it is something that everyone would benefit from regardless of language or toolkit. I know that Shawn and co. have been working towards this goal. Keep it in C, keep it simple, and keep git stupid. A solid C core is portable and easy to wrap for Python, Ruby, Perl, etc. BTW I recall that one of the first questions in this thread was "what toolkit" with proposed choices of QtCore, glib, POSIX+Msys, etc. Just my $.02 -- I feel that the POSIX + MSys combination is the most viable solution since it has already been proven by the hard work of the msysgit team. It is also the environment which is most familiar to core git developers and thus there is much benefit to staying within that world. It's also the same choice made by Shawn in his libgit efforts. The fact that git's output is identical regardless of platform (for instance, git ls-files always uses "/" as its path delimiter, even on windows) is really what has made creating portable git guis possible. Git to me is like a familiar and happy land that I know I can escape to even if I have the misfortune of being stuck on a windows machine. Thus, a system like msys that bends over backwards trying to make windows into something unix-like feels like the right way to go if you ask me. I'm *not* a windows user, though =) -- David -- 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
