Re: Why is AuthorDate displayed on git-blame?
- From
- Noam Soloveichik <inoamsol@gmail.com>
- Date
- Aug 6, 2020, 15:19 UTC
- Message-ID
- <6dabe718-6d6e-e76c-677d-f2dc4a5b83be@gmail.com>
- In-Reply-To
- <C4PPV24G8ZNK.3IYI2MQ3A262Y@ziyou>
On 06/08/2020 9:57, Raymond E. Pasco wrote:
> On Tue Aug 4, 2020 at 8:40 PM EDT, Junio C Hamano wrote: > --first-parent:: Follow only the first parent commit upon seeing a > merge commit. This option can be used to determine when a line was > introduced to a particular integration branch, rather than when it > was introduced to the history overall.
I want to make sure I understand your proposal correctly - --first-parent would still show AuthorDate, but of the *merge-commit*, and not the commit that introduced the line of code to the history overall.
If so, it's going to get the job done for commits which are applied by a merge-commit. Although I wonder what --first-parent would display for commits which are applied *not* by a merge.
Consider the linux kernel, where some of its commits are merge commits from pull requests, and some are applied patches: with different AuthorDate and CommitDate. For those commits, AuthorDate represents the date the patch was originally sent to review, not when it was introduced to the integration branch, which is represented by the CommitDate, which leads to inconsistencies.