linux-kernel - Guilt: Autotagging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080411002630.GD3838@josefsipek.net>
Date:	Thu, 10 Apr 2008 20:26:30 -0400
From:	"Josef 'Jeff' Sipek" <jeffpc@...efsipek.net>
To:	guilt@...efsipek.net
Cc:	linux-kernel@...r.kernel.org, git@...r.kernel.org
Subject: Guilt: Autotagging - aye or nay?

Greetings all!

I was trying to figure out what the default for Guilt's autotagging feature
should be.  Currently, the default is for it to be on, unless it's
overridden by an already existing config setting.

For those who may not be familiar with autotagging, here's an excerpt from
the guilt(7) man page:

	Autotagging is a feature that automatically creates unannotated tags
	for top, bottom, and base of the stack.

	On every push or pop operation (refresh is a pop followed by a
	push), Guilt updates the stack top (${branch}_top), stack bottom
	(${branch}_bottom), and stack base (${branch}_base) tags.

		Top: Top-most applied patch/commit
		Bottom: Bottom-most applied patch/commit
		Base: Commit on top of which the bottom most patch is applied

	Having these three tags, one can easily get the log/diff/other
	information only for commits that are (or are not!) part of the
	patch stack.

So far the few people (including myself for the past few months) I asked
privately, all said that they turn the feature off.

Ideas?  Comments?  Suggestions?

Josef 'Jeff' Sipek.

-- 
I think there is a world market for maybe five computers.
		- Thomas Watson, chairman of IBM, 1943.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/