Re: [ANNOUNCE] git-svn - bidirection operations between svn and git

From: Junio C Hamano <junkio@cox.net>
Date: Feb 16, 2006, 08:19 UTC
Message-ID: <7vr763emwx.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <cc723f590602160008v5fcc0e35h6d9296bd0572fac2@mail.gmail.com>

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

Show 6 quoted lines

> 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.