From: "נעם סולוביצ'יק" <inoamsol@gmail.com>
To: git@vger.kernel.org
Subject: Why is AuthorDate displayed on git-blame?
Date: Wed, 5 Aug 2020 03:18:43 +0300 [thread overview]
Message-ID: <CAAWR3A9po-zMVFdQfDs6R5F_rf0UvSyfByLj-vYZiXLb8+j4Ug@mail.gmail.com> (raw)
Hey everybody, I wonder about the decision behind git-blame and
git-annotate date that is being shown.
If I understand correctly, the AuthorDate is displayed, and I'd like
to challenge that decision. Consider the following case:
A feature branch having commits authored last week, but merged to the
main branch just today. And to the sake of discussion, let's say that
the branch has a bug.
When someone encounters the bug on the main branch, he would probably
want to know when it was introduced - the date when the bug started
to affect him. However, git-blame only shows him when the bug was
originally authored, in our case - *last-week*, which is confusing
since the main branch was working just fine back then.
So I wonder why was AuthorDate the date chosen to be displayed under
git-blame?
next reply other threads:[~2020-08-05 0:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 0:18 נעם סולוביצ'יק [this message]
2020-08-05 0:40 ` Why is AuthorDate displayed on git-blame? Junio C Hamano
2020-08-06 6:57 ` Raymond E. Pasco
2020-08-06 15:19 ` Noam Soloveichik
2020-08-06 18:13 ` Raymond E. Pasco
2020-08-06 18:17 ` Junio C Hamano
2020-08-06 18:52 ` [PATCH] blame-options.txt: document --first-parent option Raymond E. Pasco
2020-08-08 0:35 ` Why is AuthorDate displayed on git-blame? Jeff King
2020-08-05 1:59 ` brian m. carlson
2020-08-05 16:08 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAWR3A9po-zMVFdQfDs6R5F_rf0UvSyfByLj-vYZiXLb8+j4Ug@mail.gmail.com \
--to=inoamsol@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).