[Patches] [Patch #101055] Cookie.py

[Fred L. Drake, Jr.]

noreply@sourceforge.net writes:
 > I have a copy of Tim O'Malley's ,v file (in order to preserve the
 > version history).  I can either ask the SF admins to drop it into
 > the right place in the CVS repository, but will that screw up the
 > Python 1.6 tagging in some way?  (I would expect not, but who
 > knows?)

  That would have no effect on any of the Python tagging.  It's
probably worthwhile making sure there are no tags in the ,v file, but
that can be done after it gets dropped in place.
  Now, Greg Stein will tell us that dropping this into place is the
wrong thing to do.  What it *will* screw up is people asking for the
state of Python at a specific date before the file was actually added;
they'll get this file even for when it wasn't in the Python CVS tree.
I can live with that, but we should make a policy decision for the
Python tree regarding this sort of thing.

 > The second option would be for me to retrace Cookie.py's
 > development -- add revision 1.1, check in revision 1.2 with the
 > right log message, check in revision 1.3, &c.  Obviously I'd prefer
 > to not do this.

  Don't -- it's not worth it.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member