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

[GUILT][RFC] Autotagging

From
JSJosef 'Jeff' Sipek <jsipek@cs.sunysb.edu>
Date
Mar 10, 2007, 04:46 UTC
Message-ID
<11735019831915-git-send-email-jsipek@cs.sunysb.edu>
Greetings all!

Recently, it has been brought to my attention that it would be nice to be able to refer to the top/bottom/base of the patch stack in Guilt by a name instead of fishing around the log for the hash. I quickly coded up the following solution (which I call "autotagging"), which creates unannotated tags for the top (topmost applied patch), bottom (first applied patch), and base (parent of bottom) in with this naming scheme:

	${branch}_top
	${branch}_bottom
	${branch}_base

The branch name is necessary as each branch has its own series of patches, and potentially different history to begin with.

Of course, I included an option to disable this feature (see patch 2) - just set guilt.autotag=0 in your git config.

Before I merge this into Guilt master, I was hoping for some feedback. Just in case I completely missed something obvious, or perhaps there is a better way to name the branches :)

Thanks,
Josef "Jeff" Sipek.
Next: Josef 'Jeff' Sipek
Message 1 of 3 in “[GUILT][RFC] Autotagging”
  1. Josef 'Jeff' SipekMar 10, 2007
  2. 1/2 Automatically create unannotated tags for top, bottom, and base of the stackJosef 'Jeff' Sipek, Mar 10, 2007
  3. 2/2 Autotag: Read guilt.autotag config var and tag commits only if this feature is enabledJosef 'Jeff' Sipek, Mar 10, 2007

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.