obliterate functionality?

Giorgos Keramidas keramida at ceid.upatras.gr
Tue Mar 18 23:07:51 CDT 2008

On 2008-03-18 20:39, Martin Geisler <mg at daimi.au.dk> wrote:
>Bruce M Simpson <bms at incunabulum.net> writes:
>> My grounds for advocating "obliterate" in view of those points, are
>> that in the situations outlined above, people can and do make
>> mistakes, and even if "obliterate" is not guaranteed to purge all
>> copies of a "leaked" or otherwise mistakenly committed revision, the
>> accountability is there and you can say you tried to obliterate the
>> file, regardless of the downstream change-set penalties or the fact
>> that someone now has a copy of the file (the "dog ate my homework"
>> argument).
> It sounds like you want the backout command:
>     hg backout [OPTION]... [-r] REV

It would be nice if this were sufficient.  The FreeBSD project has been
asked in the past to *remove* all traces of particular files, though.
Not simply make them `invisible' in the latest tip of the tree, but
physically wipe out their existence from CVS.

More information about the Mercurial mailing list