git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philippe Joyez <philippe.joyez@cea.fr>
To: elizaretskii@gmail.com,
	git-for-windows <git-for-windows@googlegroups.com>
Cc: vdhoeven@lix.polytechnique.fr, git@vger.kernel.org
Subject: Re: requesting permission to use some Git for Windows code
Date: Thu, 27 Jul 2017 10:31:08 +0200	[thread overview]
Message-ID: <4517a3d2-5acb-e7b5-8cd6-0c5fe57811d1@cea.fr> (raw)
In-Reply-To: <83bce6b8-a5eb-4914-a2d3-edd57050bfaa@googlegroups.com>



Le 25/07/2017 à 15:53, Johannes Schindelin a écrit :
>
> It is great that you can make use of the code!
>
> As to the licensing problem, I agree it is a hassle. The biggest obstacle
> is that you have to have the consent of all the authors.
>
> You hereby have mine.
>

Many thanks Johannes for your positive personal answer but also for the
very detailed tips on how to handle this.

Le 27/07/2017 à 06:30, elizaretskii@gmail.com a écrit :
>
>
> An alternative would be for TeXmacs to use the code from GNU Emacs,
> which also supports Unicode file names on MS-Windows.  Emacs is of
> course GPL v3+, so there should be no problem with that.
>
Thanks you too Eli, for bringing up that piece of information; I'll
definitely take a look into it!

Philippe

  parent reply	other threads:[~2017-07-27  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a730cebb-1782-f32b-0b7c-253bd61475d6@cea.fr>
2017-07-25 13:53 ` requesting permission to use some Git for Windows code Johannes Schindelin
     [not found]   ` <83bce6b8-a5eb-4914-a2d3-edd57050bfaa@googlegroups.com>
2017-07-27  8:31     ` Philippe Joyez [this message]
2017-07-28  5:31   ` Brandon Casey
2017-07-28 15:26     ` Marius Storm-Olsen

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=4517a3d2-5acb-e7b5-8cd6-0c5fe57811d1@cea.fr \
    --to=philippe.joyez@cea.fr \
    --cc=elizaretskii@gmail.com \
    --cc=git-for-windows@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=vdhoeven@lix.polytechnique.fr \
    /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).