On 2/16/06, Junio C Hamano <junkio@cox.net> wrote: > Aneesh Kumar <aneesh.kumar@gmail.com> writes: > > > On 2/16/06, Junio C Hamano <junkio@cox.net> wrote: > >> > >> How about first adding a contrib/ directory and see how it goes? > > > > I am all for it. Attaching the latest gitview. This include branch and > > tag display support and also the option to save diffs in file. > > Now how do you want to proceed? I could just dump the thing in > say contrib/gitview subdirectory, and then afterwards you could > either keep feeding me patches or sending me pull requests. > > There are two downsides doing things that way: > > (1) you would lose the development history so far; > > (2) if gitview script is the only thing you care about, I > suspect you would want to have that at the project > toplevel, like the "coolest merge ever" gitk merge did, but > that is not what you will be getting. > > Ideally, if we had a proper "subproject" support, I would merge > your project with full development history so far as a > subproject, with your toplevel grafted at contrib/gitview > subdirectory. That would not have neither of the above two > downsides. But that hasn't happened yet (and that was one of > the reasons that I was reluctant initially -- I was hoping that > subproject stuff would materialize sooner). > > For now, I'd do the easy approach (easy for me, that is) with > both of the two downsides. If we end up doing "subproject" > thing, we could rectify things later, if this is OK with you. > It would be fine with me if you just drop the script to contrib/gitview directory. -aneesh - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Thu Feb 16 19:31:03 2006
This archive was generated by hypermail 2.1.8 : 2006-02-16 19:31:14 EST