Some other user change the topic, maybe removing the bad information from revision 1.13 (creating revisions up to 1.19). Still the information is available in the topic history. Therefore there should be the possibility to delete topic 1.13 without loosing the topic history (1.1 to 1.12 and 1.14 to 1.19 would be availabe but 1.13 not).

See also CurrentFunctionalityWithRevisions

-- JoergBieri - 13 May 2003

Solution I am looking for does not have to be clickable GUI - even RCS command line will be sufficient. Issue is rare, and making it command line-only will make it little more secure, I hope

-- PeterMasiar - 13 May 2003

Is there an answer to this question ? Would the same answer work with RcsLite ?

-- KeithHelfrich - 14 Dec 2006

You really, really, really, really, really don't want to do this. There is a good reason most CM systems don't let you delete revisions - rewriting history is a really bad idea.

On the other hand, eliding (hiding) revisions is a fine idea. A core implementation would work with any store implementation.

-- CrawfordCurrie - 15 Dec 2006

From CurrentFunctionalityWithRevisions

use rcs -o1.12 topic.txt to remove (o)bsolete revisions; cf man rcs. Note, that TWiki is not aware of missing revisions. Therefore

* diffs will be empty, * view will show the next available older revision.

-- PeterKlausner - 14 May 2003

This will 'remove' a specific revision from RCS. If we change storage or the versioning system, then we're at mercy of their implementation. With Subversion (and most other popular tools), the only way to purge a specific commit is to basically rebuild the repository without that commit.

-- RafaelAlvarez - 16 Aug 2008