git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Victor Engmark <victor.engmark@terreactive.ch>
Cc: Chris Perkins <cperkins@medialab.com>,
	Joshua Juran <jjuran@gmail.com>,
	Daniel Searles <daniel.paul.searles@gmail.com>,
	"Randal L. Schwartz" <merlyn@stonehenge.com>,
	Drew Northup <drew.northup@maine.edu>,
	oleganza@gmail.com, Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Daniel Searles <dsearles@medialab.com>
Subject: Re: Gitbox
Date: Thu, 14 Apr 2011 10:52:07 -0400	[thread overview]
Message-ID: <BANLkTi=n4GiD939v9G3ni4o72gt0L0EQ8w@mail.gmail.com> (raw)
In-Reply-To: <4DA7016F.5070308@terreactive.ch>

On Thu, Apr 14, 2011 at 10:15 AM, Victor Engmark
<victor.engmark@terreactive.ch> wrote:
> Excellent answer; it would be great to know in detail what would be an
> effective (and efficient, if possible) procedure for validating GPL
> compliance.

Glad you find it useful. There are some interesting FAQs in FSF's
website. And http://gpl-violations.org/faq/sourcecode-faq.html

> Something like a cartoon guide

Both why the lucky stiff and Hunter Thompson would be candidates if
they were still around.


m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- Software Architect - OLPC
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

  reply	other threads:[~2011-04-14 14:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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         ` Martin Langhoff [this message]
2011-04-15 19:21     ` Gitbox Tim Smith
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       ` Gitbox Joshua Juran
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

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='BANLkTi=n4GiD939v9G3ni4o72gt0L0EQ8w@mail.gmail.com' \
    --to=martin.langhoff@gmail.com \
    --cc=cperkins@medialab.com \
    --cc=daniel.paul.searles@gmail.com \
    --cc=drew.northup@maine.edu \
    --cc=dsearles@medialab.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jjuran@gmail.com \
    --cc=merlyn@stonehenge.com \
    --cc=oleganza@gmail.com \
    --cc=victor.engmark@terreactive.ch \
    /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).