From: Aneesh Kumar <aneesh.kumar@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] git-svn - bidirection operations between svn and git
Date: Thu, 16 Feb 2006 14:00:20 +0530 [thread overview]
Message-ID: <cc723f590602160030n498b18edla328f7c64d44c04a@mail.gmail.com> (raw)
In-Reply-To: <7vr763emwx.fsf@assigned-by-dhcp.cox.net>
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
next prev parent reply other threads:[~2006-02-16 8:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 7:38 [ANNOUNCE] git-svn - bidirection operations between svn and git Eric Wong
2006-02-16 8:01 ` Junio C Hamano
2006-02-16 8:08 ` Aneesh Kumar
2006-02-16 8:19 ` Junio C Hamano
2006-02-16 8:30 ` Aneesh Kumar [this message]
2006-02-16 9:20 ` Junio C Hamano
2006-02-16 11:20 ` Aneesh Kumar
2006-02-16 11:57 ` Petr Baudis
2006-02-16 12:01 ` Aneesh Kumar
2006-02-16 8:48 ` Eric Wong
2006-02-16 13:42 ` Eduardo Pereira Habkost
2006-02-16 19:25 ` Eric Wong
[not found] ` <43F4A4B1.4010307@blairos.org>
[not found] ` <20060216190426.GC12055@hand.yhbt.net>
[not found] ` <43F4CF5E.1010700@blairos.org>
[not found] ` <20060216194532.GA4446@Muzzle>
2006-02-16 19:47 ` [PATCH] git-svn: fix revision order when XML::Simple is not loaded Eric Wong
2006-02-16 21:44 ` Eric Wong
2006-02-17 2:13 ` [PATCH] git-svn: ensure fetch always works chronologically Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cc723f590602160030n498b18edla328f7c64d44c04a@mail.gmail.com \
--to=aneesh.kumar@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).