git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Daniel Koning <dk@danielkoning.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] blame: document actual range specifier behavior
Date: Fri, 09 Aug 2019 09:58:20 -0700
Message-ID: <xmqqblwye0nn.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <xmqqsgqbfucj.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Thu, 08 Aug 2019 10:19:24 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> ...  If anything,
> perhaps such a description should go to "git help revisions", as it
> is not just "blame" but "log". "The dots notation is not about
> date-based cutoff, unlike the --since/--until options" is shared by
> all history traversal tools.

By this, I do not necessarily mean "hence such a piece of info
should not be added to the documentation of blame".  Rather, an
explanation like "'^A' limits an operation to commits that are
topologically newer than A, while '--since=A' limits to commits that
are chronologically newer than A" is shared among "log", "blame" and
friends, and would be better to be clarified in documentation for
all of them.  Especially ...

>> +  git blame v2.6.18.. -- foo
>> +
>> +... If changes from branch `fix` were merged in after
>> +v2.6.18, the commits on `fix` which introduced those changes will appear
>> +in the output of 'git blame', even if those commits took place at an
>> +earlier time than v2.6.18.

... is a brilliant way to illustrate how "A.., i.e. topologically
newer than A" is different from "--since=A, i.e. chronologically
newer than A", whose understanding would help readers to understand
not just "blame" but "log".

Thanks.


      reply	other threads:[~2019-08-09 16:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08  0:10 Daniel Koning
2019-08-08 17:19 ` Junio C Hamano
2019-08-09 16:58   ` Junio C Hamano [this message]

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=xmqqblwye0nn.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=dk@danielkoning.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

git@vger.kernel.org list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ https://public-inbox.org/git \
		git@vger.kernel.org
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.io/gmane.comp.version-control.git
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for the project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git