From: "Josef 'Jeff' Sipek" <jsipek@cs.sunysb.edu>
To: git@vger.kernel.org
Cc: "Josef 'Jeff' Sipek" <jsipek@cs.sunysb.edu>
Subject: [PATCH 2/2] Autotag: Read guilt.autotag config var and tag commits only if this feature is enabled
Date: Fri, 9 Mar 2007 23:46:23 -0500 [thread overview]
Message-ID: <11735019832141-git-send-email-jsipek@cs.sunysb.edu> (raw)
In-Reply-To: <11735019831915-git-send-email-jsipek@cs.sunysb.edu>
Some users may not want to have guilt automatically tag the top, bottom, and
base of the stack. Allow them to disable such functionality by setting
guilt.autotag=0 in their git config file.
guilt-init now accepts a new parameter '-n' to automatically set
guilt.autotag=0 in the current repository.
Signed-off-by: Josef 'Jeff' Sipek <jsipek@cs.sunysb.edu>
---
Documentation/guilt-init.txt | 8 +++++++-
guilt | 15 +++++++++++++++
guilt-init | 15 ++++++++++++---
3 files changed, 34 insertions(+), 4 deletions(-)
diff --git a/Documentation/guilt-init.txt b/Documentation/guilt-init.txt
index e643668..a245c6e 100644
--- a/Documentation/guilt-init.txt
+++ b/Documentation/guilt-init.txt
@@ -8,12 +8,18 @@ guilt-init - Initialize guilt for use in a git repository
SYNOPSIS
--------
-'guilt-init'
+'guilt-init [-n]'
DESCRIPTION
-----------
Initialize a git repository for use with guilt
+OPTIONS
+-------
+-n::
+ Do not automatically create stack top, bottom, and base tags (sets
+ guilt.autotag config variable to 0).
+
EXAMPLES
--------
First, get a repository to work on. Here's one that we'll use as an example:
diff --git a/guilt b/guilt
index 3dbe4b6..e7c22d2 100755
--- a/guilt
+++ b/guilt
@@ -285,6 +285,11 @@ function pop_many_patches
# usage: update_stack_tags
function update_stack_tags
{
+ # bail if autotagging is not enabled
+ if [ $autotag -eq 0 ]; then
+ return 0
+ fi
+
if [ `wc -l < $applied` -gt 0 ]; then
# there are patches applied, therefore we must get the top,
# bottom and base hashes, and update the tags
@@ -480,12 +485,22 @@ function munge_hash_range
fi
}
+#
# Some constants
+#
# used for: git-apply -C <val>
guilt_push_diff_context=1
#
+# Parse any part of .git/config that belongs to us
+#
+
+# autotag?
+autotag=`git-config guilt.autotag`
+[ -z "$autotag" ] && autotag=1
+
+#
# The following gets run every time this file is source'd
#
diff --git a/guilt-init b/guilt-init
index 1277998..feacf95 100755
--- a/guilt-init
+++ b/guilt-init
@@ -5,11 +5,19 @@
DO_NOT_CHECK_BRANCH_EXISTENCE=1
+USAGE="[-n]"
. guilt
-if [ $# -ne 0 ]; then
- usage
-fi
+autotag=1
+
+while case $# in 0) break ;; esac; do
+ if [ "$1" = "-n" ]; then
+ autotag=0
+ shift
+ else
+ usage
+ fi
+done
if [ -d "$GUILT_DIR/$branch" ]; then
die "Branch $branch appears to be already initialized (GIT_DIR=$GIT_DIR)"
@@ -20,3 +28,4 @@ mkdir $GUILT_DIR/$branch
touch $GUILT_DIR/$branch/series
touch $GUILT_DIR/$branch/status
+git-config --int --replace-all guilt.autotag $autotag
--
1.5.0.3.268.g3dda
prev parent 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 [GUILT][RFC] Autotagging Josef 'Jeff' Sipek
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 ` Josef 'Jeff' Sipek [this message]
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=11735019832141-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).