git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jonathan Smith <Jonathan.Smith@fphcare.co.nz>
Cc: Junio C Hamano <gitster@pobox.com>,
	Philip Oakley <philipoakley@iee.org>,
	GitList <git@vger.kernel.org>
Subject: RE: [RFC/PATCH] Git doc: GPL2 does not apply to repo data
Date: Mon, 1 Feb 2016 08:35:22 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1602010827430.2964@virtualbox> (raw)
In-Reply-To: <6D15DFBB73355B4E9EFB1AD5EF9FCA31842442AA@NZ-EXCHANGE1.fphcare.com>

Hi Jonathan,

On Sun, 31 Jan 2016, Jonathan Smith wrote:

> I'll be taking all of your contributions as ammo as I continue to fight
> for Git here.

I would hope that it is unnecessary to point weapons at managers to
"convince" them to use Git.

In the meantime, I think we have accumulated a lot of arguments in favor
of using Git to manage source code.

For less tech-savvy managers, I found that name dropping works quite well
(read: naming a couple of well-known companies/products that switched to
Git).

Ciao,
Johannes

  reply	other threads:[~2016-02-01  7:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  3:08 GPL v2 authoritative answer on stored code as a derived work Jonathan Smith
2016-01-25 19:06 ` Junio C Hamano
2016-01-27 23:58   ` Philip Oakley
2016-01-28  8:16     ` Johannes Schindelin
2016-01-31 20:51       ` Philip Oakley
2016-01-31 21:00       ` [RFC/PATCH] Git doc: GPL2 does not apply to repo data Philip Oakley
2016-01-31 22:08         ` Junio C Hamano
2016-01-31 22:15           ` Jonathan Smith
2016-02-01  7:35             ` Johannes Schindelin [this message]
2016-02-01  7:49               ` Matthieu Moy
2016-02-01  8:14                 ` Jeff King
2016-02-01  8:16                   ` Jeff King
2016-02-01 10:57                   ` Philip Oakley
2016-02-01 10:53           ` Philip Oakley
2016-02-01 11:34             ` Philip Oakley

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=alpine.DEB.2.20.1602010827430.2964@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=Jonathan.Smith@fphcare.co.nz \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=philipoakley@iee.org \
    /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).