![](https://secure.gravatar.com/avatar/29a7f7f0cd76746320e0e94bc11cebf9.jpg?s=120&d=mm&r=g)
That's right. In practice I bisect the date instead; that way I can issue
the same command in all my svn source directories from sf.net and lbl.gov.
For example:
svn update -r "{2014-03-08 18:00}"
Nicholas K. Sauter, Ph. D.
Computer Staff Scientist, Molecular Biophysics and Integrated Bioimaging
Division
Lawrence Berkeley National Laboratory
1 Cyclotron Rd., Bldg. 33R0345
Berkeley, CA 94720
(510) 486-5713
On Mon, Jun 13, 2016 at 3:38 PM, Luc Bourhis
On 14 Jun 2016, at 00:29, Luc Bourhis
wrote: So why is it so hard to describe how to do bisection? Despite the responses on this BB trying to answer my question, I still don't have a clear understanding of how to do it. With svn it is just "svn update -r”.
I think there is a misunderstanding here. “svn update -r REV” is just “git checkout HASH”. By bisection, I understand “git bisect”, which is a way to automate finding a faulty commit. You don’t need to use that if you find it’s too complicated. Actually, "git bisect" is just some scripting on the top of "git checkout", I think.
I see what you meant! Sorry, it’s late here… You can bisect the svn rev number because they are increasing integers! _______________________________________________ cctbxbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/cctbxbb