git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joshua Juran <jjuran@gmail.com>
To: Drew Northup <drew.northup@maine.edu>
Cc: Daniel Searles <dsearles@medialab.com>,
	git@vger.kernel.org, oleganza@gmail.com
Subject: Re: Gitbox
Date: Wed, 13 Apr 2011 12:24:11 -0700	[thread overview]
Message-ID: <5F5479DB-511E-4ADC-8B71-5D7C801ECEAF@gmail.com> (raw)
In-Reply-To: <1302722214.22161.5.camel@drew-northup.unet.maine.edu>

On Apr 13, 2011, at 12:16 PM, Drew Northup wrote:

> On Wed, 2011-04-13 at 12:09 -0700, Joshua Juran wrote:
>
>> On Apr 13, 2011, at 11:59 AM, Drew Northup wrote:
>>
>>> On Wed, 2011-04-13 at 11:16 -0700, Daniel Searles wrote:
>>
>>>
>>>> I'm curious if Gitbox is in violation of the Git's GPL.
>>>> http://www.gitboxapp.com/
>>>
>>> Well, it appears that he may have implemented "git" on his own, or  
>>> at
>>> the very least he's trying to imply that he did.
>>>
>>> http://www.gitboxapp.com/faq.html#gpl
>>
>> He very clearly says that he ships Git, not a reimplementation.
>
> He also clearly stated that he's not calling git command-line tools...

I wonder why he would ship them, then.

> "Gitbox neither links (statically or dynamically) against Git nor uses
> custom interfaces to interact with it. Git binaries are provided for
> your convenience only."

Calling execve() is not dynamic linking, that I'm aware of.

> I'm hoping he'll have a more complete statement for all of us.

I think you've misinterpreted his words, but I agree that a  
clarification to set minds at ease would be appropriate.

Josh

  reply	other threads:[~2011-04-13 19:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 18:16 Gitbox Daniel Searles
2011-04-13 18:55 ` Gitbox Joshua Juran
2011-04-13 18:59 ` Gitbox Drew Northup
2011-04-13 19:09   ` Gitbox Joshua Juran
2011-04-13 19:16     ` Gitbox Drew Northup
2011-04-13 19:24       ` Joshua Juran [this message]
2011-04-13 19:41       ` Gitbox Randal L. Schwartz
2011-04-13 20:04         ` Gitbox Drew Northup
2011-04-13 20:26           ` Gitbox Taylor Hedberg
2011-04-13 20:29           ` Gitbox Joshua Juran
2011-04-13 22:56           ` Gitbox Tim Smith
2011-04-14  9:52           ` Gitbox Sitaram Chamarty
2011-04-14 10:03             ` Gitbox Vincent van Ravesteijn
2011-04-14 12:34             ` Gitbox Drew Northup
2011-04-13 20:43         ` Gitbox Junio C Hamano
     [not found]           ` <1C18B4FB-BB10-4AC7-8952-D477CB4EF289@medialab.com>
2011-04-13 22:13             ` Gitbox Randal L. Schwartz
2011-04-13 23:10           ` Gitbox Randal L. Schwartz
2011-04-13 19:18 ` Gitbox Jakub Narebski
     [not found] <BANLkTikfCDm-5Yde=2Cm-ROc1dcMwopvOg@mail.gmail.com>
2011-04-13 22:23 ` Gitbox Joshua Juran
2011-04-14  1:58   ` Gitbox Chris Perkins
2011-04-14  2:02     ` Gitbox Randal L. Schwartz
2011-04-14  2:28     ` Gitbox Chris Perkins
2011-04-14  2:34       ` Gitbox Randal L. Schwartz
2011-04-14  4:59       ` Gitbox Joshua Juran
2011-04-14 13:55     ` Gitbox Martin Langhoff
     [not found]     ` <32803572.1897.1302789371873.JavaMail.trustmail@mail1.terreactive.ch>
2011-04-14 14:15       ` Gitbox Victor Engmark
2011-04-14 14:52         ` Gitbox Martin Langhoff
2011-04-15 19:21     ` Gitbox Tim Smith

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=5F5479DB-511E-4ADC-8B71-5D7C801ECEAF@gmail.com \
    --to=jjuran@gmail.com \
    --cc=drew.northup@maine.edu \
    --cc=dsearles@medialab.com \
    --cc=git@vger.kernel.org \
    --cc=oleganza@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).