git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Josef 'Jeff' Sipek" <jsipek@cs.sunysb.edu>
To: git@vger.kernel.org
Subject: [GUILT][RFC] Autotagging
Date: Fri,  9 Mar 2007 23:46:21 -0500	[thread overview]
Message-ID: <11735019831915-git-send-email-jsipek@cs.sunysb.edu> (raw)

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.

             reply	other threads:[~2007-03-10  4:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-10  4:46 Josef 'Jeff' Sipek [this message]
2007-03-10  4:46 ` [PATCH 1/2] Automatically create unannotated tags for top, bottom, and base of the stack Josef 'Jeff' Sipek
2007-03-10  4:46 ` [PATCH 2/2] Autotag: Read guilt.autotag config var and tag commits only if this feature is enabled Josef 'Jeff' Sipek

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=11735019831915-git-send-email-jsipek@cs.sunysb.edu \
    --to=jsipek@cs.sunysb.edu \
    --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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).