On Wed, 11 Aug 2010 17:50 +0100, "Jonathan Lange" <j...@mumak.net> wrote: > On Wed, Aug 11, 2010 at 5:30 PM, Peter Westlake > <peter.westl...@pobox.com> wrote: > > In the Git version of the Twisted source code, there are tags for > > releases, e.g. the revision with SHA id > > 85a6a0f9e3c4ea22d1d72d4ca8eb0c08ee99ca85 corresponds to 8.0.0. This is > > good, but there aren't any intermediate changes on that branch (tag?), > > just the releases! So there isn't much for "git bisect" to work with. > > I'm trying to trace a bug that wasn't in 2.5.0 but is in 8.0.0; what > > arguments should I give to bisect? Apologies if this is obvious to > > anyone who knows how to use git, but I'm just a beginner. > > > > I don't know about git, but the way I'd do it in Bazaar is: > bzr bisect -r svn:19165..svn:23025 run <script> > > Where <script> is something that tests for the bug. > > Revision numbers obtained from > http://twistedmatrix.com/trac/wiki/ReleaseRevisions;
Excellent, thanks! The revision numbers are just what I need. Peter. > bzr-bisect from > https://launchpad.net/bzr-bisect; bzr-svn from > https://launchpad.net/bzr-svn. > > jml > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
