git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Raymond E. Pasco" <ray@ameretat.dev>,
	"נעם סולוביצ'יק" <inoamsol@gmail.com>,
	git@vger.kernel.org
Subject: Re: Why is AuthorDate displayed on git-blame?
Date: Fri, 7 Aug 2020 20:35:00 -0400	[thread overview]
Message-ID: <20200808003500.GA3751874@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqq1rkjljus.fsf@gitster.c.googlers.com>

On Thu, Aug 06, 2020 at 11:17:31AM -0700, Junio C Hamano wrote:

> "Raymond E. Pasco" <ray@ameretat.dev> writes:
> 
> > Perhaps the following
> > adaptation:
> >
> > --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.
> 
> Yup.  We somehow forgot to document it when we did 95a4fb0e (blame:
> handle --first-parent, 2015-09-15).  The text reads well.

My fault. I think I imagined it would just be included along with other
rev-list options, but the text above makes it clear why we'd want to
talk specifically about how it applies to blame.

-Peff

  parent reply	other threads:[~2020-08-08  0:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05  0:18 Why is AuthorDate displayed on git-blame? נעם סולוביצ'יק
2020-08-05  0:40 ` 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       ` Jeff King [this message]
2020-08-05  1:59 ` Why is AuthorDate displayed on git-blame? 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=20200808003500.GA3751874@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=inoamsol@gmail.com \
    --cc=ray@ameretat.dev \
    /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).