From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, dgutov@yandex.ru, Emacs-devel@gnu.org
Subject: web pages in CVS [was Re: Accessible "building from source" instructions]
Date: Mon, 27 May 2019 13:12:00 -0400 [thread overview]
Message-ID: <e3imtvddpb.fsf_-_@fencepost.gnu.org> (raw)
In-Reply-To: <37a2ad08-7441-19ff-b6f9-a289cb21601d@cs.ucla.edu> (Paul Eggert's message of "Mon, 27 May 2019 09:59:31 -0700")
Paul Eggert wrote:
> How much would it cost to convert Savannah's web pages to Git? Is it
> time for a pity fundraiser?
Maintaining infrastructure sure is a thankless task.
It's a www.gnu.org issue, not a Savannah issue.
Implement a two-way sync from git to CVS today if you like. Ref eg
http://lists.gnu.org/r/savannah-hackers-public/2013-04/msg00022.html
http://lists.gnu.org/archive/html/bug-gnulib/2012-12/msg00072.html
next prev parent reply other threads:[~2019-05-27 17:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 23:34 Accessible "building from source" instructions Dmitry Gutov
2019-05-26 0:25 ` T.V Raman
2019-05-26 8:19 ` Dmitry Gutov
2019-05-26 1:30 ` Paul Eggert
2019-05-26 8:20 ` Dmitry Gutov
2019-05-26 8:50 ` Paul Eggert
2019-05-26 10:18 ` Dmitry Gutov
2019-05-26 14:46 ` Eli Zaretskii
2019-05-26 20:08 ` Paul Eggert
2019-05-27 2:29 ` Eli Zaretskii
2019-05-27 16:59 ` Paul Eggert
2019-05-27 17:12 ` Glenn Morris [this message]
2019-05-27 17:24 ` Eli Zaretskii
2019-05-27 20:17 ` Richard Stallman
2019-05-27 20:11 ` Richard Stallman
2019-05-26 9:23 ` Andreas Schwab
2019-05-26 10:01 ` Paul Eggert
2019-05-26 10:54 ` Andreas Schwab
2019-05-26 20:11 ` Paul Eggert
2019-05-26 20:19 ` Andreas Schwab
2019-05-27 4:55 ` Paul Eggert
2019-05-26 2:42 ` Eli Zaretskii
2019-05-26 8:25 ` Dmitry Gutov
2019-05-26 16:36 ` Eli Zaretskii
2019-05-26 22:10 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3imtvddpb.fsf_-_@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=dgutov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.