[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master e7c105fd73: ; Mention git bisect's --first-parent in admin/notes/
From: |
Gerd Moellmann |
Subject: |
master e7c105fd73: ; Mention git bisect's --first-parent in admin/notes/repo |
Date: |
Tue, 1 Nov 2022 05:26:37 -0400 (EDT) |
branch: master
commit e7c105fd73dbede4d00c1f26ad2273d49fabd0da
Author: Gerd Möllmann <gerd@gnu.org>
Commit: Gerd Möllmann <gerd@gnu.org>
; Mention git bisect's --first-parent in admin/notes/repo
---
admin/notes/repo | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/admin/notes/repo b/admin/notes/repo
index 2185c5a003..afba3dca8f 100644
--- a/admin/notes/repo
+++ b/admin/notes/repo
@@ -128,6 +128,11 @@ again.
This is a semi-automated way to find the revision that introduced a bug.
Browse 'git help bisect' for technical instructions.
+Depending on what you want to do, it can be helpful to start bisecing
+with the option '--first-parent', like `git bisect start
+--first-parent', which makes bisect ignore commits coming into a
+branch from merges.
+
* Maintaining ChangeLog history
Older ChangeLog entries are kept in history files named ChangeLog.1,
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- master e7c105fd73: ; Mention git bisect's --first-parent in admin/notes/repo,
Gerd Moellmann <=