All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ferrell <bferrell@baywinds.org>
To: Jeff King <peff@peff.net>, Robert P Fischer <rpf2116@columbia.edu>
Cc: git@vger.kernel.org
Subject: Re: Apple violating git LGPL?
Date: Wed, 06 Aug 2014 12:53:56 -0700	[thread overview]
Message-ID: <53E287D4.1050106@baywinds.org> (raw)
In-Reply-To: <20140806184304.GB21254@peff.net>

On 08/06/2014 11:43 AM, Jeff King wrote:

snippage here 8< >8
> As it happens, though, they _do_ modify the git that they distribute. I know at least that they bake-in the osxkeychain helper config in away that the user cannot turn off. There 
> may be more changes, but I haven't done a full diff. And they do provide the source: https://www.opensource.apple.com/source/Git/
Is that a plugin?  if not what about proprietary plugins? How are they affected by the license is this case?

  reply	other threads:[~2014-08-06 20:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06 18:10 Apple violating git LGPL? Robert P Fischer
2014-08-06 18:36 ` Charles Bailey
2014-08-06 18:43 ` Jeff King
2014-08-06 19:53   ` Bruce Ferrell [this message]
2014-08-06 20:51     ` Jeff King
2014-08-06 20:23   ` Tony
2014-08-06 20:41     ` Jeff King

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=53E287D4.1050106@baywinds.org \
    --to=bferrell@baywinds.org \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=rpf2116@columbia.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.