From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs-devel@gnu.org, dgutov@yandex.ru
Subject: Re: Accessible "building from source" instructions
Date: Mon, 27 May 2019 09:59:31 -0700 [thread overview]
Message-ID: <37a2ad08-7441-19ff-b6f9-a289cb21601d@cs.ucla.edu> (raw)
In-Reply-To: <835zpw3a0p.fsf@gnu.org>
Eli Zaretskii wrote:
>> Yesterday I solved my problem in the usual way: I used a search engine and found
>> a cheat sheet somewhere.
> The CVS manual includes such a cheat sheet.
No doubt it does, but I didn't find it with a quick look and it was easier for
me to use a search engine.
> Of course, there's also the Emacs VC, which still supports CVS. You
> can even do "C-x v v" without knowing what exactly does it do.
Yes, but this requires setting up the local CVS repository in the first place
which C-x v v doesn't do. Plus, I don't use C-x v v even for Git, so I'd need to
relearn C-x v v's quirks. Plus, Fedora no longer ships CVS by default, so I had
to install CVS first. And most likely there was another minor roadblock that
I've forgotten.
We each have our own way of using Git, and it's inevitable that one must do
things differently with CVS. Of course CVS works eventually, but we'd be better
off using the same version-control system with web pages as we do for code, and
it's a bit discouraging that Savannah's web pages are still stuck on CVS.
How much would it cost to convert Savannah's web pages to Git? Is it time for a
pity fundraiser?
next prev parent reply other threads:[~2019-05-27 16:59 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 [this message]
2019-05-27 17:12 ` web pages in CVS [was Re: Accessible "building from source" instructions] Glenn Morris
2019-05-27 17:24 ` Accessible "building from source" instructions 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=37a2ad08-7441-19ff-b6f9-a289cb21601d@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=Emacs-devel@gnu.org \
--cc=dgutov@yandex.ru \
--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.