[PATCH v2 0/2] Avoid hardcoded "good"/"bad" bisect terms
- From
- Jonas Rebmann <kernel@schlaraffenlan.de>
- Date
- Mar 23, 2026, 22:48 UTC
- Message-ID
- <20260323-bisect-terms-v2-0-8d6bdb2c9c7e@schlaraffenlan.de>
While checking whether all output messages of git bisect where covered by [PATCH 1/2] bisect: use selected alternate terms in status output I found hardcoded good/bad refs leading to incompatibility of git rev-parse --bisect with alternate bisect run terms. This is addressed by [PATCH 2/2] rev-parse: use selected alternate terms too look up refs
Signed-off-by: Jonas Rebmann <kernel@schlaraffenlan.de> --- Changes in v2: - Improve commit message - Add tests - Include second patch for hardcoded good/bad in rev-parse - Link to v1: https://lore.kernel.org/r/20260320-bisect-terms-v1-1-c30c9540542a@schlaraffenlan.de
---
Jonas Rebmann (2):
bisect: use selected alternate terms in status output
rev-parse: use selected alternate terms too look up refsbuiltin/bisect.c | 23 +++++++++++++---------- builtin/rev-parse.c | 8 ++++++-- t/t6030-bisect-porcelain.sh | 16 ++++++++++++++-- 3 files changed, 33 insertions(+), 14 deletions(-) --- base-commit: 1eceb487f285f1efa78465e6208770318f9f4892 change-id: 20260320-bisect-terms-76036676769c
Best regards, -- Jonas Rebmann <kernel@schlaraffenlan.de>