Re: gitview 0.3

Aneesh Kumar <aneesh.kumar@gmail.com> writes:

We _could_ make a contrib/gitview directory to keep it there, and as somebody else comes up with a new interesting git application, add a new directory in contrib/ to expand that area.

But personally I am not enthused about keeping other peoples' projects in git.git tree [*1*]. I'd rather see you start your own public repository, propagate your changes from there, and run it as your own project.

Even though it is currently a single file 'project', you will want to add more stuff, maybe splitting the code to use your own *.py module to import into the main program, and add *.c files to interface with the lower level and Makefile to describe the build rules once we start libifying git. I suspect we are all better off if we keep separate projects separate in the long run.

Somebody (I think it was Sean Estabrooks but I may be mistaken) once offered to host git projects at a site he controls. I wonder if you can get him interested...

[Footnote]

*1* I was not too happy to see gitk merged in with "the coolest merge ever" myself, but that was done before my time. "Not too happy" does not necessarily mean I object to it. All things considered I think it was a good thing: (1) as a showcase of how cool a merge can be, it was a good demonstration; (2) coming with a repository browser usable out-of-box with minimum dependencies was a good thing (tcl/tk is pretty much available universally for easy install); (3) it is a good example program of how a repository browser can be done.