{"thread":{"id":"5492","subject":"stgit bisect feature request","startedAt":"2006-09-05T23:49:15Z","lastAt":"2006-09-06T08:36:20Z","messageCount":3,"participants":["Torgil Svensson","Karl Hasselström","Catalin Marinas"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"26382","messageId":"e7bda7770609051649j56a92085i8d8a73ab12004c43@mail.gmail.com","threadId":"5492","inReplyTo":null,"subject":"stgit bisect feature request","fromName":"Torgil Svensson","fromEmail":"torgil.svensson@gmail.com","sentAt":"2006-09-05T23:49:15Z","receivedAt":"2006-09-05T23:49:15Z","isPatch":false,"sender":{"key":"torgil.svensson@gmail.com","avatar":null},"body":"I think i'd be nice if stgit wraps bisect and you could write\n$ stg bisect start\n$ stg bisect bad\n$ stg bisect good ORIG_HEAD\n\nand after bisect checks out the files it pushes the current stack as\nif you had used stg pull at this point\n\n//Torgil\n"},{"id":"26392","messageId":"20060906083153.GA19001@diana.vm.bytemark.co.uk","threadId":"5492","inReplyTo":"e7bda7770609051649j56a92085i8d8a73ab12004c43@mail.gmail.com","subject":"Re: stgit bisect feature request","fromName":"Karl Hasselström","fromEmail":"kha@treskal.com","sentAt":"2006-09-06T08:31:53Z","receivedAt":"2006-09-06T08:31:53Z","isPatch":false,"sender":{"key":"kha@treskal.com","avatar":"https://gravatar.com/avatar/f0120c734b5279b345075a28521e1ac66acb20c9913ffe9bf6ae97e53f7f3f13?d=mp&s=160"},"body":"On 2006-09-06 01:49:15 +0200, Torgil Svensson wrote:\n\n> I think i'd be nice if stgit wraps bisect and you could write\n>\n> $ stg bisect start\n> $ stg bisect bad\n> $ stg bisect good ORIG_HEAD\n>\n> and after bisect checks out the files it pushes the current stack as\n> if you had used stg pull at this point\n\nYes, this sounds very useful for bisecting when you can't test the old\nrevisions as-is, e.g. because you have to patch for an unrelated bug,\nor because you need a patch to trigger the problem.\n\n-- \nKarl Hasselström, kha@treskal.com\n      www.treskal.com/kalle\n"},{"id":"26393","messageId":"tnxfyf5qtmj.fsf@arm.com","threadId":"5492","inReplyTo":"e7bda7770609051649j56a92085i8d8a73ab12004c43@mail.gmail.com","subject":"Re: stgit bisect feature request","fromName":"Catalin Marinas","fromEmail":"catalin.marinas@arm.com","sentAt":"2006-09-06T08:36:20Z","receivedAt":"2006-09-06T08:36:20Z","isPatch":false,"sender":{"key":"catalin.marinas@arm.com","avatar":null},"body":"\"Torgil Svensson\" <torgil.svensson@gmail.com> wrote:\n> I think i'd be nice if stgit wraps bisect and you could write\n> $ stg bisect start\n> $ stg bisect bad\n> $ stg bisect good ORIG_HEAD\n>\n> and after bisect checks out the files it pushes the current stack as\n> if you had used stg pull at this point\n\nIt would be nice but there could be conflicts when pushing patches,\nespecially if you do the bisect over a larger range of commits. It\ngets difficult if some StGIT patches rely on features not present some\nof the commits you are checking.\n\nHave you tried this idea manually (or with some scripts) and found it\nfeasible?\n\n-- \nCatalin\n"}]}