git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
* git blame --ignore-rev to accept tree objects
@ 2020-08-04  7:40 Amir Yalon
  2020-08-04 15:19 ` Junio C Hamano
  0 siblings, 1 reply; 2+ messages in thread
From: Amir Yalon @ 2020-08-04  7:40 UTC (permalink / raw)
  To: git

Dear list members,

In the manual entry for blame.ignoreRevsFile in git-config(1) it says “unabbreviated object name”, which misled me into thinking I could specify tree objects rather than commit objects. This got me thinking, how useful it could be, to be able to include detailed instructions how to ignore a particular commit *in its own commit message*. Right now, it is practically impossible to do, because one can’t know the commit object name in advance. However, once the tree object name is known, it’s easy to include in the commit message.

How practical would it be to implement this feature? How bad could it be, if some unrelated commits with the same tree would be skipped unintentionally by git-blame as a result?

Regards,
Amir

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: git blame --ignore-rev to accept tree objects
  2020-08-04  7:40 git blame --ignore-rev to accept tree objects Amir Yalon
@ 2020-08-04 15:19 ` Junio C Hamano
  0 siblings, 0 replies; 2+ messages in thread
From: Junio C Hamano @ 2020-08-04 15:19 UTC (permalink / raw)
  To: Amir Yalon; +Cc: git

"Amir Yalon" <amiryal-mljwnltxmo@yxejamir.net> writes:

> How practical would it be to implement this feature? How bad could it be, if some unrelated commits with the same tree would be skipped unintentionally by git-blame as a result?

I would say it would be horrible, if the instruction to skip a wrong
commit is baked into the commit object and cannot be corrected
without rewriting history.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-08-04 15:19 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-04  7:40 git blame --ignore-rev to accept tree objects Amir Yalon
2020-08-04 15:19 ` Junio C Hamano

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://7fh6tueqddpjyxjmgtdiueylzoqt6pt7hec3pukyptlmohoowvhde4yd.onion/inbox.comp.version-control.git
	nntp://ie5yzdi7fg72h7s4sdcztq5evakq23rdt33mfyfcddc5u3ndnw24ogqd.onion/inbox.comp.version-control.git
	nntp://4uok3hntl7oi7b4uf4rtfwefqeexfzil2w6kgk2jn5z2f764irre7byd.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 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