unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Gregory Heytings <gregory@heytings.org>
Cc: marmot-te@riseup.net, 46236@debbugs.gnu.org, rms@gnu.org
Subject: bug#46236: 26.1; explicit the info files installation
Date: Wed, 21 Apr 2021 09:13:06 -0500	[thread overview]
Message-ID: <CADwFkmmp45QhPz-g7vH9sCACbXZzk3z7vnuEZfRn-5o9=-cgbw@mail.gmail.com> (raw)
In-Reply-To: <192e82f20f3b71f5def0@heytings.org>

Gregory Heytings <gregory@heytings.org> writes:

>> But I think the Debian maintainers might be upset, and it would be easy
>> for them to then disable this functionality.
>
> Why would they be?  They already distribute these files in a separate
> package, so AFAICS they have no reason to prevent their users from doing
> the same.

I mean, I don't know, obviously.

But we would in a sense short-circuit their [IMO incorrect, pedantic and
damaging] decision to mark GFDL manuals "non-free".





  reply	other threads:[~2021-04-21 14:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 14:10 bug#46236: 26.1; explicit the info files installation marmot-te
2021-02-03  5:48 ` Richard Stallman
2021-04-21  3:20   ` Stefan Kangas
2021-04-21  9:02     ` Eli Zaretskii
2021-04-21 12:06       ` Stefan Kangas
2021-04-21 12:16         ` Eli Zaretskii
2021-04-21 12:40           ` Stefan Kangas
2021-04-21 15:32             ` Glenn Morris
2021-04-21 16:34               ` Stefan Kangas
2021-04-21 12:32         ` Gregory Heytings
2021-04-21 13:00           ` Eli Zaretskii
2021-04-21 13:47             ` Gregory Heytings
2021-04-21 13:11           ` Stefan Kangas
2021-04-21 13:54             ` Gregory Heytings
2021-04-21 14:13               ` Stefan Kangas [this message]
2021-03-06 14:25 ` Tomas Nordin
2021-03-07  6:11   ` 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='CADwFkmmp45QhPz-g7vH9sCACbXZzk3z7vnuEZfRn-5o9=-cgbw@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=46236@debbugs.gnu.org \
    --cc=gregory@heytings.org \
    --cc=marmot-te@riseup.net \
    --cc=rms@gnu.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.
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).