{"thread":{"id":"10299","subject":"[PATCH] rev-list documentation: add \"--bisect-all\".","startedAt":"2007-10-16T03:59:05Z","lastAt":"2007-10-16T10:42:57Z","messageCount":2,"participants":["Christian Couder","Ralf Wildenhues"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"55939","messageId":"20071016055905.55c1d280.chriscool@tuxfamily.org","threadId":"10299","inReplyTo":null,"subject":"[PATCH] rev-list documentation: add \"--bisect-all\".","fromName":"Christian Couder","fromEmail":"chriscool@tuxfamily.org","sentAt":"2007-10-16T03:59:05Z","receivedAt":"2007-10-16T03:59:05Z","isPatch":true,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Signed-off-by: Christian Couder <chriscool@tuxfamily.org>\n---\n Documentation/git-rev-list.txt |   16 ++++++++++++++++\n 1 files changed, 16 insertions(+), 0 deletions(-)\n\n\tLe lundi 15 octobre 2007, Frank Lichtenheld a écrit :\n\t>\n\t> --bisect-all is still missing a Documentation/ patch.\n\n\tThanks for catching that. \n\tHere is a patch.\n\ndiff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt\nindex 7cd0e89..f6dd0c4 100644\n--- a/Documentation/git-rev-list.txt\n+++ b/Documentation/git-rev-list.txt\n@@ -34,6 +34,7 @@ SYNOPSIS\n \t     [ \\--pretty | \\--header ]\n \t     [ \\--bisect ]\n \t     [ \\--bisect-vars ]\n+\t     [ \\--bisect-all ]\n \t     [ \\--merge ]\n \t     [ \\--reverse ]\n \t     [ \\--walk-reflogs ]\n@@ -354,6 +355,21 @@ the expected number of commits to be tested if `bisect_rev`\n turns out to be bad to `bisect_bad`, and the number of commits\n we are bisecting right now to `bisect_all`.\n \n+--bisect-all::\n+\n+This outputs all the commit objects between the included and excluded\n+commits, ordered by their distance to the included and excluded\n+commits. The farthest from them is displayed first. (This is the only\n+one displayed by `--bisect`.)\n+\n+This is usefull because it makes it easy to choose a good commit to\n+test when you want to avoid to test some of them for some reason (they\n+may not compile for example).\n+\n+This option can be used along with `--bisect-vars`, in this case,\n+after all the sorted commit objects, there will be the same text as if\n+`--bisect-vars` has been used alone.\n+\n --\n \n Commit Ordering\n-- \n1.5.3.4.213.g68ad5\n"},{"id":"56009","messageId":"20071016104257.GB1170@ins.uni-bonn.de","threadId":"10299","inReplyTo":"20071016055905.55c1d280.chriscool@tuxfamily.org","subject":"Re: [PATCH] rev-list documentation: add \"--bisect-all\".","fromName":"Ralf Wildenhues","fromEmail":"ralf.wildenhues@gmx.de","sentAt":"2007-10-16T10:42:57Z","receivedAt":"2007-10-16T10:42:57Z","isPatch":true,"sender":{"key":"ralf.wildenhues@gmx.de","avatar":null},"body":"Hello,\n\nA couple of typos:\n\n* Christian Couder wrote on Tue, Oct 16, 2007 at 05:59:05AM CEST:\n> \n> diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt\n> index 7cd0e89..f6dd0c4 100644\n> --- a/Documentation/git-rev-list.txt\n> +++ b/Documentation/git-rev-list.txt\n[...]\n> @@ -354,6 +355,21 @@ the expected number of commits to be tested if `bisect_rev`\n>  turns out to be bad to `bisect_bad`, and the number of commits\n>  we are bisecting right now to `bisect_all`.\n>  \n> +--bisect-all::\n> +\n> +This outputs all the commit objects between the included and excluded\n> +commits, ordered by their distance to the included and excluded\n> +commits. The farthest from them is displayed first. (This is the only\n> +one displayed by `--bisect`.)\n> +\n> +This is usefull because it makes it easy to choose a good commit to\n\ns/usefull/useful/\n\n> +test when you want to avoid to test some of them for some reason (they\n> +may not compile for example).\n> +\n> +This option can be used along with `--bisect-vars`, in this case,\n> +after all the sorted commit objects, there will be the same text as if\n> +`--bisect-vars` has been used alone.\n\ns/has/had/\n\nCheers,\nRalf\n"}]}