From: "Shawn O. Pearce" <spearce@spearce.org>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Pierre Habouzit <madcoder@debian.org>,
Elijah Newren <newren@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Nicolas Pitre <nico@fluxnic.net>,
Alex Riesen <raa.lkml@gmail.com>,
Eric Wong <normalperson@yhbt.net>, Git List <git@vger.kernel.org>
Subject: Re: git fast-import/fast-export
Date: Sat, 6 Mar 2010 13:43:21 -0800 [thread overview]
Message-ID: <20100306214321.GD2529@spearce.org> (raw)
In-Reply-To: <fabb9a1e1003061105u70cf87b8h579fe154a24fb8f0@mail.gmail.com>
Sverre Rabbelier <srabbelier@gmail.com> wrote:
> On Sat, Mar 6, 2010 at 20:02, Junio C Hamano <gitster@pobox.com> wrote:
> > Isn't fast-import designed to be used as a downstream side of a pipe that
> > is fed by an independent program you write (and may link with libsvn)? ?It
> > wouldn't care what license that data producer program is distributed under.
>
> Yes, I'm not worried about using the 'git-fast-import' or the
> 'git-fast-export' binary, I want to use-and-modify the parsing code to
> work as a fast-import/fast-export frontend to svn _on top_ of using
> those binaries..
Oh. Yuck.
I guess I can give my blessing to relicense anything in fast-import
that I've written from GPLv2 to GPLv2 or v3. But as Dscho points
out, there are many authors in even the parsing code. You will
need to get consent from all of them.
--
Shawn.
next prev parent reply other threads:[~2010-03-06 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 15:02 git fast-import/fast-export Sverre Rabbelier
2010-03-06 15:29 ` Johannes Schindelin
2010-03-06 19:02 ` Junio C Hamano
2010-03-06 19:05 ` Sverre Rabbelier
2010-03-06 21:43 ` Shawn O. Pearce [this message]
2010-03-06 21:45 ` Sverre Rabbelier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100306214321.GD2529@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=madcoder@debian.org \
--cc=newren@gmail.com \
--cc=nico@fluxnic.net \
--cc=normalperson@yhbt.net \
--cc=raa.lkml@gmail.com \
--cc=srabbelier@gmail.com \
/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.
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 NNTP newsgroup(s).