[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RCS: (vc-next-action 1) only New Backend

From: Eli Zaretskii
Subject: Re: RCS: (vc-next-action 1) only New Backend
Date: Sat, 19 Sep 2015 12:23:25 +0300

> From: David Kastrup <address@hidden>
> Cc: Eli Zaretskii <address@hidden>,  address@hidden
> Date: Sat, 19 Sep 2015 10:59:24 +0200
> IIRC VC was given some significant surgery around the time where Emacs
> was migrated to a Git repository in order to better support file-set
> check-ins and various workflows for distributed version control systems.
> I seem to remember that some RCS-only features were debated and possibly
> dropped at that time because ESR (along with a lot of others) were not
> terribly sympathetic towards complicating the generic framework because
> of the possibility of its continued use (mostly expected to be due to
> nostalgia).  Indeed, I switched to using Git even for private one-person
> projects a long time ago myself.

However, the Emacs manual still says it's possible:

  When you give a prefix argument to `vc-next-action' (`C-u C-x v v'), it
  still performs the next logical version control operation, but accepts
  additional arguments to specify precisely how to do the operation.

     * You can specify the name of a version control system.  This is
       useful if the fileset can be managed by more than one version
       control system, and Emacs fails to detect the correct one.

     * Otherwise, if using CVS or RCS, you can specify a revision ID.

       If the fileset is modified (or locked), this makes Emacs commit
       with that revision ID.  You can create a new branch by supplying an
       appropriate revision ID (*note Branches::).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]