mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Bagas Sanjaya <>
Cc: Junio C Hamano <>,
	Eric Sunshine <>,
	Stefan Beller <>,
	"Dr . Matthias St . Pierre" <>,
	Bagas Sanjaya <>
Subject: [PATCH v5 1/2] blame: describe default output format
Date: Fri,  8 Oct 2021 16:16:13 +0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

While there is descriptions for porcelain and incremental output
formats, the default format isn't described. Describe that format for
the sake of completeness.

Signed-off-by: Bagas Sanjaya <>
 Documentation/git-blame.txt | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt
index 3bf5d5d8b4..08008f4a60 100644
--- a/Documentation/git-blame.txt
+++ b/Documentation/git-blame.txt
@@ -93,6 +93,19 @@ include::blame-options.txt[]
 	is used for a caret to mark the boundary commit.
+When neither `--porcelain` nor `--incremental` option is specified,
+`git blame` will output annotation for each line with:
+- abbreviated object name for the commit the line came from;
+- author ident (by default author name and date, unless `-s` or `-e` is
+specified); and
+- line number
+before the line contents.
An old man doll... just what I always wanted! - Clara

  reply	other threads:[~2021-10-08  9:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08  9:16 [PATCH v5 0/2] blame: documentation update Bagas Sanjaya
2021-10-08  9:16 ` Bagas Sanjaya [this message]
2021-10-08  9:16 ` [PATCH v5 2/2] blame: document --color-* options Bagas Sanjaya
2021-10-19 12:31   ` [PATCH] git config doc: fix recent ASCIIDOC formatting regresison Ævar Arnfjörð Bjarmason
2021-10-19 21:11     ` Jeff King
2021-10-20 15:35       ` Junio C Hamano
2021-10-08 21:09 ` [PATCH v5 0/2] blame: documentation update Junio C Hamano

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).