From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Can't start new branch in VC with RCS
Date: Tue, 19 Jan 2016 20:19:18 +0200 [thread overview]
Message-ID: <83io2pbffd.fsf@gnu.org> (raw)
In-Reply-To: <87egddy7op.fsf@nyu.edu> (message from allan gottlieb on Tue, 19 Jan 2016 09:17:58 -0500)
> From: allan gottlieb <gottlieb@nyu.edu>
> Date: Tue, 19 Jan 2016 09:17:58 -0500
>
> >> 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.
> >
> > What version of Emacs is that?
>
> 24.5
The upcoming 25.1 will fix this.
prev parent reply other threads:[~2016-01-19 18:19 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
2016-01-12 3:29 ` Eli Zaretskii
2016-01-19 14:17 ` allan gottlieb
2016-01-19 18:19 ` Eli Zaretskii [this message]
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=83io2pbffd.fsf@gnu.org \
--to=eliz@gnu.org \
--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).