unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Chris <chrisl_ak@hotmail.com>
Subject: Re: RCS revert to previous version
Date: Mon, 14 Oct 2002 07:07:41 -0000	[thread overview]
Message-ID: <Xns92A6EB0DF7753chrislak@216.168.3.40> (raw)
In-Reply-To: 5l8z12e8i5.fsf@rum.cs.yale.edu

on 13 Oct 2002, "Stefan Monnier <foo@acm.com>"
<monnier+gnu.emacs.help/news/@flint.cs.yale.edu> spake thusly: 

>>>> If I am working on, say 1.7 of a document using RCS, what is the
>>>> easiest way to revert to a specific version, say 1.4 as an example?
>>> 
>>> What do you mean by "revert" ?
>>> In your example, when you say you want to revert to 1.6, which
>>> of the following options do you mean:
>>> - you simply want the content of the file to be the same as the
>>> one in version 1.6 (and it will be committed as 1.9 if you ever
>>> commit it, at which point 1.6 and 1.9 would be the same)
>>> - you really want to get back to the time when 1.6 was the latest
>>> and simply discard 1.7 and 1.8 (i.e. after reverting to 1.6,
>>> modifying the file and committing it, it'd be committed as 1.7).
>>> - you want to go back to the time of 1.6 but without discarding
>>> 1.7 and 1.8, such that after modifying the file, it will be
>>> committed as 1.6.1.1 (i.e. first version on a new branch named
>>> 1.6.1). 
>>> - yet something else.
> 
>> I want to "revert" as in "go back" to a previous version. Discarding
>> all changes in between. I don't care what the new revision number is
>> when I check the document back in. I care about the content. Most of
>> your other scenarios don't match any meaning of the word "revert"
>> that I am aware of, but hopefully this makes it clearer. I want to be
>> able to say "oops, this is all wrong, let's go back three versions
>> and begin again." 
> 
> All three scenarios are the same as far as the file's content is
> concerned. The difference is in the history information kept in the
> RCS file itself. 

Fine. And since I am going back and starting over, I don't care about the 
version numbers or the comments for versions that have been discarded and 
are unrecoverable... so either having those entries disappear entirely 
and going back to the next available version number (i.e. I revert to 1.4 
and the next checkin makes it 1.5) OR whatever needs to be done (i.e. if 
I have to keep at version 1.8 for the next checkin despite 1.5-1.7 no 
longer existing) would be fine. Unless there is some recoverable text 
(which in this case there would not be) then I am not really interested 
in retaining history information about that unrecoverable text :)

  reply	other threads:[~2002-10-14  7:07 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
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 [this message]
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=Xns92A6EB0DF7753chrislak@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).