From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: xfq <xfq.free@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: About the web pages repository
Date: Sat, 20 Apr 2013 12:22:28 +0200 [thread overview]
Message-ID: <87ehe5wlgb.fsf@zigzag.favinet> (raw)
In-Reply-To: <CAAF+z6HrJt_P3HqnTwpeOO0qimz4tTQx5__EPc4KxpeyJ8qgtw@mail.gmail.com> (xfq's message of "Sat, 20 Apr 2013 14:49:34 +0800")
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
() xfq <xfq.free@gmail.com>
() Sat, 20 Apr 2013 14:49:34 +0800
Why is the web pages repo of Emacs still using CVS? I cannot find
the original post for this decision, and I know commits to the web
pages repo are less often than the sources repo. But I think it is
more convenient and maintainable to use one VCS for a project
(Emacs).
The web paegs for all GNU packagess are currently maintained w/ CVS.
Emacs is not special, here.
On my (tertiary) TODO list is asking for (read-only) access to the web
server in order to document the current maintenance (creation, update)
protocol in the form of a tarball (of scripts) + .texi, for offline
analysis, redesign, and testing. The goal is to raise the protocol's
abstractions and expose a simple configuration item (to savannah) so
that each project's maintainers could choose the VCS for its web pages,
much as they can currently choose the VCS for its source code.
Maybe someone else w/ more time and expertise (in web stuff) can do this
job before me; i for one certainly would not mind (hint hint).
Once that is in place, we can commence Emacs-specific (i.e., multi-year,
circular, exhausting) discussion on which VCS to use for the web pages,
maybe.
--
Thien-Thi Nguyen
GPG key: 4C807502
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-04-20 10:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 6:49 About the web pages repository xfq
2013-04-20 10:22 ` Thien-Thi Nguyen [this message]
2013-04-20 11:11 ` xfq
2013-04-21 0:00 ` Stephen J. Turnbull
2013-04-21 9:02 ` Thien-Thi Nguyen
2013-04-21 18:25 ` chad
2013-04-21 18:28 ` Glenn Morris
2013-04-21 18:38 ` chad
2013-04-22 2:32 ` Richard Stallman
2013-05-01 0:17 ` Ted Zlatanov
2013-05-01 12:41 ` Xue Fuqiao
2013-05-01 15:39 ` Ted Zlatanov
2013-04-20 14:59 ` [OFFTOPIC] " Stefan Monnier
2013-04-20 10:50 ` Andreas Schwab
2013-04-20 18:10 ` Glenn Morris
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=87ehe5wlgb.fsf@zigzag.favinet \
--to=ttn@gnuvola.org \
--cc=emacs-devel@gnu.org \
--cc=xfq.free@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).