On 8/11/07, Steffen Prohaska <prohaska@xxxxxx> wrote: > >> [..list of tools and links] > > > > Thank you for the information! i'll check those up. > > > I hope to have an improved list on monday, sorted by priority of > the developers I'm working with. > > I thought I do some coding, to find out a bit more about the > stability of msysgit. So I started and added support for kdiff3 > on Windows (see patches in separate mail). neat.The hardest part for me was to find out that I didn't have to configure anything or add a command line option to get kdiff3 running. (I cheated looking in the source, I think we should add #ifdef __MINGW32__ / #endif around the registry reading part. Good job! > I'm impressed. Pretty much everything I tried today worked for > me. After I got git gui running, and learned how to avoid pitfalls > of git submodule, development went smoothly. I pushed and pulled a > bit from linux and mac and did some coding. Thanks for the vim > setup! > > I think you (and more people I don't yet know) did a great job > with msysgit. I'd recommend it over cygwin's git, which caused > some trouble for me. Thanks. I'm as fresh as you in msysgit development but it is quite straightforward. I've fiddled around with cygwin/msys before but now I think we're on to something useful. > > What do you include in the "make windist" installer and the "Windows > > support" ? Are you talking porcelain or plumbing? > > Hard to say. I believe now, from what I learned today, that the msysgit > approach is quite reasonable: Grouping all needed unix tools around a > submodule containing git. But the submodule should be git.git. I think > this is what I'd expect. I like the idea of bringing everything needed > along, and keeping it separate from the rest of the system. This avoids > conflicts with, for example, cygwin. > I don't think I would expect much more for a basic setup. All tests > should run, maybe some msysgit tests would be needed to test the > pitfalls I'm lacking several things. Many usability-glitches, some bugs, easy access to documentation. Also we want to integrate the mingw git parts into git.git so people can follow the official repo. etc.. > I didn't like the submodule problems I ran into and I still didn't find > out how to push to the git mob branch. This is weird. I haven't had such problems with this (dirty submodule in working dir), but that probably is because the supermodule doesn't depend on files in the submodule [submodule "make install" copies files to the supermodule]. Otherwise we should be more dependent on a clean submodule state. I would though expect a "git reset --hard" to fix up the submodule for me. > [ many proposals for future work with msysgit] Yeah. there's plenty of stuff to do. You could add this stuff to the issue tracker Dimitry has initiated. //Torgil - 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
