From: Chris <chrisl_ak@hotmail.com>
Subject: Re: RCS revert to previous version
Date: Sat, 12 Oct 2002 01:44:09 -0000 [thread overview]
Message-ID: <Xns92A4B44CB9660chrislak@216.168.3.40> (raw)
In-Reply-To: m3r8ewhnea.fsf@mandala.local
on 11 Oct 2002, Jhair Tocancipa Triana <jhair_tocancipa@gmx.net> spake
thusly:
> Chris writes:
>
> > Right... but my question is how to make that the current
> > version... do I have to delete the entirety of my current working
> > file and copy and paste from the older version window? I can't
> > just check the older version in and have it become the latest. I
> > was hoping there was a more efficient way than copy and paste...
>
> Is this, what you need?
>
> ,----[ C-h k C-x v u ]
>| C-x v u runs the command vc-revert-buffer
>| which is an interactive autoloaded Lisp function in `vc'.
>| [Arg list not available until function definition is loaded.]
>|
>| Revert the current buffer's file back to the version it was based on.
>| This asks for confirmation if the buffer contents are not identical
>| to that version. This function does not automatically pick up newer
>| changes found in the master file; use C-u C-x v v to do so.
Well, this command reverts the current buffer back to the state when it
was last checked out. Which can be handy, but is not what I am looking
for. Let me take another stab at explaining. I have a document that has
gone through these changes (numbers are version numbers):
1.5
Bob went to school
1.6
Mary went home
1.7
John went to the market
1.8
Chris discovers emacs (and then fire)
I open the document (1.8) and discover that I need to go back to version
1.6. How best to do this? I can open 1.6 up using the show-other-version
command, but then I have to select everything in the old display document
and paste it "over" the new document. It just seemed to me there must be
a better way of going back more than one revision.
Maybe I am just missing something really stupid... or maybe this is just
not needed very often. But the ability to revert back more than one
version seems very useful to me.
next prev parent reply other threads:[~2002-10-12 1:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 8:03 RCS revert to previous version Chris
2002-10-11 11:00 ` Colin Marquardt
2002-10-11 16:42 ` Chris
2002-10-11 17:54 ` Jhair Tocancipa Triana
2002-10-12 1:44 ` Chris [this message]
2002-10-12 7:31 ` MH
2002-10-12 9:51 ` Jhair Tocancipa Triana
2002-10-13 2:41 ` Chris
2002-10-12 18:56 ` Stefan Monnier <foo@acm.com>
2002-10-13 2:37 ` Chris
2002-10-13 14:08 ` Stefan Monnier <foo@acm.com>
2002-10-14 7:07 ` Chris
2002-10-14 10:48 ` Lee Sau Dan
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=Xns92A4B44CB9660chrislak@216.168.3.40 \
--to=chrisl_ak@hotmail.com \
/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).