[Top][All Lists]

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

Re: Feature request: When revisioning config files... (Brian Cady)

From: David Levner
Subject: Re: Feature request: When revisioning config files... (Brian Cady)
Date: Thu, 21 Mar 2024 01:56:39 +0000 (UTC)


I can't speak for the RCS maintainers about incorporating your suggestions into RCS. I have found it convenient to write wrapper scripts that improve my RCS experience. For example, my scripts contain a 'putlock' command that stores a revision of a file and immediately locks the file so I can continue working on it. I also have an 'edit' command that locks a file and opens it in a text editor. It would be easy to combine these two commands to create a 'putlockedit' command.

For me, the biggest convenience is my 'put' command. When I type 'put file.ext', rcsdiff is run on file.ext and its output is written into a temporary file that opens in a text editor. I then review all the changes I've made since the last revision and write a multi-line description of my changes. Once I save the temporary file and close the text editor, file.txt is unlocked and my description of the changes is recorded in the RCS file.

David Levner

On Wednesday, March 20, 2024 at 12:01:41 PM EDT, <> wrote:

Send help-rcs mailing list submissions to

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to

You can reach the person managing the list at

When replying, please edit your Subject line so it is more specific
than "Re: Contents of help-rcs digest..."

Today's Topics:

  1. Feature request: When revisioning config files... (Brian Cady)


Message: 1
Date: Tue, 19 Mar 2024 16:42:38 +0000
From: Brian Cady <>
To: "" <>
Subject: Feature request: When revisioning config files...
Content-Type: text/plain; charset=utf-8 would be great if there was an option to leave the config source file in place when storing a version, instead of deleting the source file. In this way the to-be-modified config file could then be edited in safety, knowing that one could fall back to the back-up in /RCS/.
    Even better would be an option which would open the config file in emacs/vim/nano/etc at the same time as storing the old version at /RCS/. In this way only one step would get one to modifying config files while backing up the old version. One might then rapidly and reversably attempt modification to fix a config problem.



Subject: Digest Footer

help-rcs mailing list


End of help-rcs Digest, Vol 129, Issue 1

reply via email to

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