From: Andre Spiegel <spiegel@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: patch for documentation about version control
Date: Wed, 10 Nov 2004 10:22:36 +0100 [thread overview]
Message-ID: <1100078556.3428.151.camel@localhost> (raw)
In-Reply-To: <jkpt2mf58r.fsf@glug.org>
On Wed, 2004-11-10 at 04:00 -0500, Thien-Thi Nguyen wrote:
> although RCS is old (and somewhat quirky), it is still
> useful. i'm about to check in the following (changing
> the names to have vc-rcs- prefix), which should extend
> the lifetime of RCS ,v files if not the RCS executable
> programs installed in ${bindir}, for a while yet.
Please don't add this. RCS is perfectly alive and kicking, and to add
an alternative means of manipulating the master files (with subtle
incompatibilities admitted) is just plain unnecessary.
If you can use your parsing functions to make vc-annotate work under
RCS, that is a fine improvement, but please (a) let me see your patches
before you commit them, and (b) version control operations on RCS files
should always go via the actual RCS commands.
next prev parent reply other threads:[~2004-11-10 9:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 6:55 patch for documentation about version control Alex Ott
2004-11-09 9:13 ` Andre Spiegel
2004-11-12 9:11 ` Alex Ott
2004-11-09 18:21 ` Karl Fogel
2004-11-09 21:32 ` Stefan Monnier
2004-11-09 21:34 ` Stefan Monnier
2004-11-09 22:09 ` David Kastrup
2004-11-10 9:00 ` Thien-Thi Nguyen
2004-11-10 9:22 ` Andre Spiegel [this message]
2004-11-10 16:43 ` Thien-Thi Nguyen
2004-11-11 11:55 ` Andre Spiegel
2004-11-11 15:11 ` Stefan
2004-11-11 15:36 ` Andre Spiegel
2004-11-11 15:25 ` Thien-Thi Nguyen
2004-11-11 16:06 ` Thien-Thi Nguyen
2004-11-11 18:25 ` Thien-Thi Nguyen
2004-11-11 20:59 ` Andre Spiegel
2004-11-12 9:33 ` Thien-Thi Nguyen
2004-11-10 9:30 ` Andre Spiegel
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=1100078556.3428.151.camel@localhost \
--to=spiegel@gnu.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 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.