From: Dale Snell <ddsnell@frontier.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Can't start new branch in VC with RCS
Date: Mon, 11 Jan 2016 16:52:36 -0800 [thread overview]
Message-ID: <20160111165236.4948b323@zothique.localdomain> (raw)
In-Reply-To: <87h9ij6b44.fsf@nyu.edu>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
On Mon, 11 Jan 2016 16:48:43 -0500, in message 87h9ij6b44.fsf@nyu.edu,
allan gottlieb wrote:
> I have a single file class-notes.html (with RCS/class-notes.html,v).
> I am using rcs in default (locking) mode
>
> The head revision is 8.6. I am the only user and the head revision is
> locked by me. C-x v = shows the one simple change I made since 8.6.1
> and the file has been saved.
>
> I want to start branch 8.6.1. The manual suggests C-u C-x v v.
>
> C-u x v v asks for a new backend. I do not want to change backends.
> If I type RCS, it correctly reports that RCS is the current backend
> and exits. If I try 8.6.1, it correctly reports that there is no
> match (it is looking for a backend).
>
> Is this supposed to be possible under VC for RCS? I presumably could
> achieve my goal using rcs directly from the command line.
>
> Thanks in advance.
> allan
>
Hi Allan,
For the record, I was unable to coerce, cajole, or otherwise
convince VC to create new branches in RCS. I had to use the
command line. It wasn't hard to do, but it would have been nice
if VC had the capability. Perhaps it does and we just haven't see
it?
--Dale
--
Sign in coffee shop: "Children left unattended will be given an
espresso and a Free Puppy."
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-01-12 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 21:48 Can't start new branch in VC with RCS allan gottlieb
2016-01-12 0:52 ` Dale Snell [this message]
2016-01-12 3:29 ` Eli Zaretskii
2016-01-19 14:17 ` allan gottlieb
2016-01-19 18:19 ` Eli Zaretskii
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=20160111165236.4948b323@zothique.localdomain \
--to=ddsnell@frontier.com \
--cc=help-gnu-emacs@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.
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).