From: "Steve Frécinaux" <nudrema@gmail.com>
To: "Todd Zullinger" <tmz@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Using git from Python
Date: Wed, 14 May 2008 08:10:05 +0200 [thread overview]
Message-ID: <f35478f50805132310p2b94b128o3a6f391849ffb8ec@mail.gmail.com> (raw)
In-Reply-To: <20080513205021.GI2592@inocybe.teonanacatl.org>
On Tue, May 13, 2008 at 10:50 PM, Todd Zullinger <tmz@pobox.com> wrote:
> Hi Steve,
>
> I saw that you started some python bindings for git and thought I'd
> take a peak (even though I don't have a need for such a thing at the
> moment :). I notice that the COPYING file is GPLv2, but the comments
> in all the files say License: LGPL 2. Which one is incorrect?
Mmh. The LGPL one. I think I've copied the wrong file in and forgot to
double-test ;-)
prev parent reply other threads:[~2008-05-14 6:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 0:18 Using git from Python Asheesh Laroia
2008-05-08 3:54 ` Eric Hanchrow
2008-05-08 4:23 ` David Aguilar
2008-05-10 6:52 ` Dill
2008-05-12 18:17 ` Asheesh Laroia
2008-05-13 7:39 ` Steve Frécinaux
[not found] ` <20080513205021.GI2592@inocybe.teonanacatl.org>
2008-05-14 6:10 ` Steve Frécinaux [this message]
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=f35478f50805132310p2b94b128o3a6f391849ffb8ec@mail.gmail.com \
--to=nudrema@gmail.com \
--cc=git@vger.kernel.org \
--cc=tmz@pobox.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).