unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jeff Walsh <fejfighter@gmail.com>,
	 Yuuki Harano <masm+github@masm11.me>,
	 emacs-devel@gnu.org
Subject: Re: gsettings.m4 copyright
Date: Mon, 03 Jan 2022 21:28:26 +0800	[thread overview]
Message-ID: <87ee5pdk3p.fsf@yahoo.com> (raw)
In-Reply-To: <83fsq5c6qs.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 03 Jan 2022 15:02:19 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> You are saying that we cannot include it in Emacs, because whoever
> wrote the code didn't contribute it to us?  That's not a copyright
> question, that's a completely different (and more serious) issue.

Yes, I was.  Thanks.

> Jeff and Yuuki, would you please tell us how you got this file and who
> has the copyright to its code?

I'm neither of those, but that file is from glib, in m4macros/

  https://gitlab.gnome.org/GNOME/glib/-/blob/main/m4macros/gsettings.m4

There is no copyright statement in that file, but GLib as a whole,
according to the COPYING file, is under the LGPLv2.1.  (It's part of
GNOME as well, but I don't know if Glib specifically is part of the GNU
project.)  If it's urgent, I can rewrite it tomorrow.

And I'm really sorry I didn't catch that when merging feature/pgtk to
master.

According to the VCS history, the following people wrote the file:

  - Bastien Nocera
  - Allison Karlitskaya
  - Dan Winship
  - Javier Jardón
  - Colin Walters
  - Matthias Clasen
  - Christian Persch
  - Hib Eris
  - Simon McVittie
  - Philip Withnall

I will try to get emails for those people tomorrow.



  reply	other threads:[~2022-01-03 13:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r19pgl3x.fsf.ref@yahoo.com>
2022-01-03 10:38 ` gsettings.m4 copyright Po Lu
2022-01-03 12:53   ` Eli Zaretskii
2022-01-03 12:56     ` Po Lu
2022-01-03 13:02       ` Eli Zaretskii
2022-01-03 13:28         ` Po Lu [this message]
2022-01-03 13:39         ` Yuuki Harano
2022-01-03 14:29           ` Eli Zaretskii
2022-01-03 15:11             ` Eli Zaretskii
2022-01-03 15:59               ` Yuuki Harano
2022-01-04  8:35                 ` Yuuki Harano
2022-01-04 13:29                   ` Eli Zaretskii
2022-01-03 16:03             ` Stefan Monnier
2022-01-03 17:26               ` Eli Zaretskii
2022-01-03 23:56         ` Richard Stallman
2022-01-04  3:31           ` Eli Zaretskii
2022-01-04  3:48           ` Stefan Kangas
2022-01-05  3:53             ` Richard Stallman

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: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87ee5pdk3p.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=fejfighter@gmail.com \
    --cc=masm+github@masm11.me \
    /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://git.savannah.gnu.org/cgit/emacs.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).