cvs commit: src/sbin/ping ping.8 ping.c src/share/man/man4 inet.4 ip.4 src/sys/netinet in.h in_pcb.h ip.h ip_input.c ip_output.c ip_var.h src/usr.bin/netstat inet.c

[Peter Jeremy]

On Thu, Apr 03, 2003 at 12:47:17AM +1000, Stephen McKay wrote:
>On Tuesday, 1st April 2003, Mike Silbersack wrote:
>>>   Implement support for RFC 3514 (The Security Flag in the IPv4 Header).
>>>   (See: ftp://ftp.rfc-editor.org/in-notes/rfc3514.txt)
>>
>>Actually committing to the tree is taking this joke quite a bit too far.
>>Is repo-surgery planned to remove this?
>
>Can we have this invisibly un-commited?

If you mean "make it so it never happened" then I don't believe this
is possible.  To explain, the change means that ping.c (for example)
has gone from rev 1.91 to rev 1.92 - and this change has been fairly
widely disseminated:  Lots of people will have CVSup'd it and it's
in the CTM history.  If it "never happened" then ping.c will revert
to rev 1.91 (etc).  Firstly, I believe CVS doesn't cope well with
this sort of thing.  Secondly, the next person to commit to ping.c
will create rev 1.92 - meaning that there are two different rev 1.92
versions in existence.

Whatever happens, the "undo" has to increment the CVS revisions.  This
can most easily be done either by mdodd@ reverting his change
normally.  If necessary, cvs@ could then perform some surgery to mean
that ping.c 1.92 doesn't exist (though this will cause pain for anyone
who has 1.92 checked out).

IMHO, this joke isn't so off-colour that it has to disappear from the
repository.  I agree that this joke has probably outlived its purpose
but a normal backout should be sufficient for this.

Peter