git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: KOLANICH <kolan_n@mail.ru>
To: git@vger.kernel.org
Cc: Junio Hamano <gitster@pobox.com>,
	Derrick Stolee <dstolee@microsoft.com>, Jeff King <peff@peff.net>,
	Elijah Newren <newren@gmail.com>
Subject: Could /Documentation/technical/commit-graph.txt be relicensed under a permissive license?
Date: Tue, 10 Dec 2019 22:31:18 +0300	[thread overview]
Message-ID: <E2770343-BB39-458C-835E-04F0753783C3@mail.ru> (raw)

Hello. https://github.com/git/git/blob/master/Documentation/technical/commit-graph.txt documents a file format for exporting commit graphs for consumption by third-party tools. But the license of this file is not permissive, and the license of git itself is GPL, so I am not allowed to use these 2 files to create an own permissive-licensed tool reading this file. This probably defeats the purpose of exporting these info and then reading it with another applications.

Could the doc file be relicensed under a permissive license?

             reply	other threads:[~2019-12-10 20:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10 19:31 KOLANICH [this message]
2019-12-10 20:10 ` Could /Documentation/technical/commit-graph.txt be relicensed under a permissive license? Junio C Hamano
2019-12-10 20:38   ` Derrick Stolee
2019-12-10 20:50     ` Jeff King
2019-12-10 17:18       ` Ed Maste
2019-12-10 20:58       ` Derrick Stolee
2019-12-10 22:20       ` Junio C Hamano
2019-12-11  0:36         ` KOLANICH
2019-12-11 12:57           ` Johannes Schindelin
2019-12-13  0:58       ` brian m. carlson
2019-12-15  2:29     ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E2770343-BB39-458C-835E-04F0753783C3@mail.ru \
    --to=kolan_n@mail.ru \
    --cc=dstolee@microsoft.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=newren@gmail.com \
    --cc=peff@peff.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).