Re:Why do you not make the code available under a 'source co...
by emeraldd on Wednesday June 17, 2015 @01:15PM
(#9733542)
I know it's svn is just an example but:
http://git-scm.com/docs/git-svn
The svn plugin to git let's have a git repo that is a clone /client of an svn repo. Very handy if you have an svn upstream but need to work offline.
Re:Why do you not make the code available under a 'source co...
by jeltz on Wednesday June 17, 2015 @02:00PM
(#9733920)
Git, Mercurial, Darcs, Monotone, and Baazar all have a built-in bisect and for svn there are well used external scripts (like svn-bisect).
Re:Why do you not make the code available under a 'source co...
by nqzero on Wednesday June 17, 2015 @01:13PM
(#9733524)
git bisect automates the process, but the underlying technique should work with any VCS. and i've scripted it up in SVN several times to good effect
Re:Why do you not make the code available under a 'source co...
by kazinator on Wednesday June 17, 2015 @01:44PM
(#9733805)
Git has bisect because Torvalds and co. did the same thing outside of version control using kernel tarballs.
"Hmm, it still worked in 2.2.13, but not in 2.2.37. Let's try 2.2.25."
Re:Why do you not make the code available under a 'source co...
by MaulingMonkey on Wednesday June 17, 2015 @01:26PM
(#9733655)
I've been in situations where I was desperate enough to do it by hand. 20+ builds and manual tests later, I found a really nasty bug in some 3rd party code that manifested with the most bizarre repro that had no obvious connection even in hindsight, and symptoms involving cleanly exit(3)ing out of the program from a totally unrelated bit of code.
Heck git allows you to edit the history pretty widely, right (I have only limited experience with git myself)? So in this case he could maintain a separate upstream repository which only contains the releases, with all the intermediate commits sanitized.