From: Michael Lyons <git@michael.lyo.nz>
To: git@vger.kernel.org
Cc: Michael Lyons <git@michael.lyo.nz>
Subject: [PATCH 0/1] doc: git-bisect to synopsis
Date: Sun, 11 Jan 2026 15:42:47 -0500 [thread overview]
Message-ID: <20260111204316.836446-1-git@michael.lyo.nz> (raw)
Update the format of bisect. This one was less involved than git-blame.
Should I be changing any code blocks to [synopsis] as well?
There might also be formatting changes desired among the "Bisect run" exit codes.
Michael Lyons (1):
doc: git-bisect: convert to new doc format
Documentation/git-bisect.adoc | 67 ++++++++++++++++++-----------------
1 file changed, 34 insertions(+), 33 deletions(-)
--
2.47.3
next reply other threads:[~2026-01-11 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-11 20:42 Michael Lyons [this message]
2026-01-11 20:42 ` [PATCH 1/1] doc: git-bisect: convert to new doc format Michael Lyons
2026-01-12 3:13 ` Junio C Hamano
2026-01-12 21:23 ` Jean-Noël AVILA
2026-01-13 12:54 ` Junio C Hamano
2026-01-13 18:45 ` Jean-Noël Avila
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260111204316.836446-1-git@michael.lyo.nz \
--to=git@michael.lyo.nz \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox