On 10/20/13 7:59 AM, Adrian Crum wrote: > With Tortoise SVN it's easy. Right-click on your local copy, > select Tortoise SVN -> Show Log. Right-click on your commit, > select Revert changes from this revision. Commit. > Yeah, I can fairly easily just revert. But then I have to redo svn copy and re-apply all the changes. That will end up creating some needless noise in the revision history and it is also some tedious work I would like to avoid if other [math] committers are OK with the "forward fix" approach ;) I understand fully and will fully revert if anyone objects to this approach.
Phil > Adrian Crum > Sandglass Software > www.sandglass-software.com > > On 10/19/2013 11:22 PM, Phil Steitz wrote: >> I inadvertently committed some WIP on Kolmogorov-Smirnov test >> implementation (MATH-437) in r1533853, in which I meant only to fix >> some javadoc in BinomialConfidenceInterval. The commit copies the >> existing implementation from the distribution package and makes some >> mods to it. I did it this way to preserve history of the code that >> is being kept. The code is not finished, has some checkstyle >> issues, but it should build OK. I am not sure exactly how to undo >> this in svn so I can redo it later and I would prefer to just edit >> the commit log and finish the code that I was planning to commit >> later in subsequent commits. Are people OK with this, or should I >> try to back out the copy / add? >> >> Maybe I need some of that git "change-stashing" capability ;) >> >> On the other hand, I am sure I will manage to screw up git commits >> in myriad other ways... >> >> Phil >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
