...
[Tim]
>> What revision was your laptop at before the update? It could help a
>> lot to know the earliest revision at which this fails.
[Brett]
> No clue. I had not updated my local version in quite some time since most
> of my dev as of late has been at work.
A good clue is to look at the "Revsion: NNNNN" line from "svn info"
output executed from the root of your checkout. Or if you have the
Python executable handy:
>>> import sys
>>> sys.subversion
('CPython', 'trunk', '46762')
No, I'm not making that up!
>> ...
>> Doing a binary search under SVN should be very easy, given that
>> a revision number identifies the entire state of the repository.
> That would be handy. Question is do we just want a progressive backtrack or
> an actual binary search that goes back a set number of revisions and then
> begins to creep back up in rev. numbers when it realizes it has gone back
> too far.
What we really want to do is solve the problem. If we're going to tie
up my machine doing it, I want as few builds as theoretically
possible. If we're going to tie up your machine, it's fine by me if
it goes back one checkin at a time until 1991 :-)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4