From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: bug#19299: 25.0.50; "Contributing" button in *About GNU Emacs* no longer works
Date: Wed, 10 Dec 2014 03:34:02 -0600 [thread overview]
Message-ID: <85y4qf7ss5.fsf@stephe-leake.org> (raw)
In-Reply-To: <837fy0wv2w.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 09 Dec 2014 20:12:55 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Glenn Morris <rgm@gnu.org>
>> Cc: flexibeast@gmail.com, emacs-devel@gnu.org
>> Date: Tue, 09 Dec 2014 12:55:59 -0500
>>
>> Eli Zaretskii wrote:
>>
>> > You mean, we shouldn't be concerned that this information will not be
>> > available to users of a popular platform?
>>
>> No, that's neither what I mean nor what the situation would be.
>> I meant that we should not let how Debian choose to split their packages
>> (and repositories) influence where we put Emacs information.
>
> Now I'm confused. If we put this in the manual, then Debian users
> will not see it.
Unless they take the extra steps of adding 'non-free' to their
distribution list, and installing the Emacs documentation.
I think this is an important issue. Remember, the point of this file is
to encourage Emacs users to contribute bug reports/patches/etc to Emacs;
we want it to be easily available to everyone.
--
-- Stephe
next prev parent reply other threads:[~2014-12-10 9:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <21636.57684.129193.880930@a1i15.kph.uni-mainz.de>
[not found] ` <l7egsaulbz.fsf@fencepost.gnu.org>
2014-12-09 0:06 ` bug#19299: 25.0.50; "Contributing" button in *About GNU Emacs* no longer works Stephen Leake
[not found] ` <slsigpq0hz.fsf@fencepost.gnu.org>
2014-12-09 0:12 ` Stephen Leake
2014-12-09 0:21 ` Alexis
2014-12-09 4:43 ` Glenn Morris
2014-12-09 8:37 ` Stephen Leake
2014-12-09 16:22 ` Eli Zaretskii
2014-12-09 17:55 ` Glenn Morris
2014-12-09 18:12 ` Eli Zaretskii
2014-12-10 9:34 ` Stephen Leake [this message]
2014-12-10 16:18 ` Richard Stallman
2014-12-10 17:15 ` Stephen Leake
2014-12-15 8:39 ` 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=85y4qf7ss5.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=emacs-devel@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).