On Thu, Feb 21, 2008 at 11:25 PM, Dan Price <[EMAIL PROTECTED]> wrote: > On Thu 21 Feb 2008 at 11:15PM, Shawn Walker wrote: > > It seems I flubbed up a bit and typo'd a constant name in four spots > > in depot.py for bug 255: > > Review looks fine. If you send me this as an "hg export", it'll > be formatted such that I can commit it and have the commit show > up as you.
Attached. > > This never revealed itself during the review, hg nits, my own checks, > > or "make test" sadly. > > This is one of the things I really dislike about python. Count me in then. > > So what's the process for fixing bad commits? > > Just fix the bug :) I guess I was asking what I needed to do to the original bug, etc. ? Thanks for understanding, -- Shawn Walker, Software and Systems Analyst http://binarycrusader.blogspot.com/ "To err is human -- and to blame it on a computer is even more so." - Robert Orben
255-fix.export
Description: Binary data
_______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
