git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Guilt: Autotagging - aye or nay?

From
JSJosef 'Jeff' Sipek <jeffpc@josefsipek.net>
Date
Apr 11, 2008, 00:26 UTC
Message-ID
<20080411002630.GD3838@josefsipek.net>
In-Reply-To
<20080411000143.GC3838@josefsipek.net>
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.
Previous: Josef 'Jeff' Sipek
Message 2 of 2 in “[ANNOUNCE] Guilt v0.30”
  1. Josef 'Jeff' SipekApr 11, 2008
  2. Guilt: Autotagging - aye or nay?Josef 'Jeff' Sipek, Apr 11, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.