From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 31384@debbugs.gnu.org, Vlad Vladov <zloyzig@gmail.com>
Subject: bug#31384: Create a more visible link to official source code branch on official website
Date: Mon, 15 Jul 2019 11:47:00 +0200 [thread overview]
Message-ID: <m2wogjsk8b.fsf@gmail.com> (raw)
In-Reply-To: <87h87qugtx.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Sat, 13 Jul 2019 16:52:58 +0200")
>>>>> On Sat, 13 Jul 2019 16:52:58 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
Larsi> Vlad Vladov <zloyzig@gmail.com> writes:
>> I think it would make it easier for others to find source code and
>> contribute to the project as there are a lot of different forks of
>> emacs available and it is better to make it clear which is the
>> official one (For example there are couple of links to github if you
>> google emacs source code rather than savannah).
Larsi> Yes, I agree. Could somebody who knows how the gnu.org web page stuff
Larsi> works fix https://www.gnu.org/software/emacs/download.html
Larsi> which says
Larsi> "GNU Emacs development is hosted on savannah.gnu.org. "
Larsi> to something that mentions "source code"?
I can push the following, if thatʼs what you want (and Iʼm strongly
hoping that vc will Do The Right Thing™, because my CVS neurons were
purged a decade ago).
Index: download.html
===================================================================
RCS file: /web/emacs/emacs/download.html,v
retrieving revision 1.16
diff -u -r1.16 download.html
--- download.html 13 Jun 2019 15:42:04 -0000 1.16
+++ download.html 15 Jul 2019 09:43:20 -0000
@@ -77,7 +77,7 @@
key from Nicolas Petton <nicolas@petton.fr>, fingerprint <code>28D3 BED8 51FD F3AB 57FE F93C 2335 87A4 7C20 7910</code> (until 25.3) or <code>D405 AA2C 862C 54F1 7EEE 6BE0 E8BC D786 6AFC F978</code> (since 26.1), which can be found in the <a href="https://ftp.gnu.org/gnu/gnu-keyring.gpg">GNU keyring</a>.
</p>
- <p>GNU Emacs development is hosted on
+ <p>GNU Emacs source code and development is hosted on
<a href="http://savannah.gnu.org/projects/emacs/">savannah.gnu.org</a>.
</p>
next prev parent reply other threads:[~2019-07-15 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 3:47 bug#31384: Create a more visible link to official source code branch on official website Vlad Vladov
2019-07-13 14:52 ` Lars Ingebrigtsen
2019-07-14 1:49 ` Glenn Morris
2019-07-15 9:47 ` Robert Pluim [this message]
2019-07-15 9:55 ` Lars Ingebrigtsen
2019-07-15 10:43 ` Robert Pluim
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=m2wogjsk8b.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=31384@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=zloyzig@gmail.com \
/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).