From: sean <seanlkml@sympatico.ca>
To: git <git@vger.kernel.org>
Subject: git-commit: allow From: line to be entered in commit message
Date: Thu, 12 Jan 2006 09:37:00 -0500 [thread overview]
Message-ID: <BAYC1-PASMTP117A18814EAAFACFE0F31DAE270@CEZ.ICE> (raw)
Message-ID: <20060112093700.1d3d25db.seanlkml@sympatico.ca> (raw)
Mostly just for comment to see if there is any support
for this feature....
Sean
---
Use the author name and email information given as the
first line of the commit message in the form of:
From: name <email>
as the author's name and email address in the resulting
commit object. This makes committing foreign patches
a little less cumbersome to handle for some workflows.
diff --git a/git-commit.sh b/git-commit.sh
index 193feeb..6004cd4 100755
--- a/git-commit.sh
+++ b/git-commit.sh
@@ -219,7 +219,7 @@ t)
fi
esac
-grep -v '^#' < "$GIT_DIR"/COMMIT_EDITMSG |
+grep -v '^#' < "$GIT_DIR"/COMMIT_EDITMSG | sed -e '1s/^[ \t]*from:.*//I' |
git-stripspace > "$GIT_DIR"/COMMIT_MSG
if cnt=`grep -v -i '^Signed-off-by' "$GIT_DIR"/COMMIT_MSG |
@@ -227,6 +227,13 @@ if cnt=`grep -v -i '^Signed-off-by' "$GI
wc -l` &&
test 0 -lt $cnt
then
+ FROM=$(grep -v '^#' < "$GIT_DIR"/COMMIT_EDITMSG | sed -ne '1s/from:[ \t]*\(.*\)/\1/Ip;q')
+ NAME=$(echo "$FROM" | sed -e 's/<.*//;s/[ \t]*$//')
+ EMAIL=$(echo "$FROM" | sed -e 's/.*<\(.*\)>.*/\1/')
+ if test -n "$FROM"; then
+ export GIT_AUTHOR_NAME="$NAME"
+ export GIT_AUTHOR_EMAIL="$EMAIL"
+ fi
tree=$(git-write-tree) &&
commit=$(cat "$GIT_DIR"/COMMIT_MSG | git-commit-tree $tree $PARENTS) &&
git-update-ref HEAD $commit $current &&
next reply other threads:[~2006-01-12 14:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060112093700.1d3d25db.seanlkml@sympatico.ca>
2006-01-12 14:37 ` sean [this message]
[not found] ` <20060112102123.581e373e.seanlkml@sympatico.ca>
2006-01-12 15:21 ` git-commit: allow From: line to be entered in commit message sean
2006-01-12 20:13 ` Junio C Hamano
2006-01-12 21:53 ` Andreas Ericsson
2006-01-12 22:15 ` Junio C Hamano
[not found] ` <20060112214307.174f5719.seanlkml@sympatico.ca>
2006-01-13 2:43 ` sean
[not found] ` <20060112213207.05d76b28.seanlkml@sympatico.ca>
2006-01-13 2:32 ` sean
2006-01-13 4:03 ` Junio C Hamano
[not found] ` <20060112230633.0858694a.seanlkml@sympatico.ca>
2006-01-13 4:06 ` sean
2006-01-13 4:35 ` Junio C Hamano
[not found] ` <20060112235103.42665813.seanlkml@sympatico.ca>
2006-01-13 4:51 ` sean
2006-01-13 11:11 ` Artem Khodush
2006-01-13 17:40 ` Junio C Hamano
[not found] ` <20060113125404.58c4ce30.seanlkml@sympatico.ca>
2006-01-13 17:54 ` sean
2006-01-13 19:51 ` Junio C Hamano
2006-01-13 21:53 ` Johannes Schindelin
2006-01-12 19:00 ` Joel Becker
2006-01-12 20:22 ` Junio C Hamano
2006-01-13 6:58 ` Joel Becker
2006-01-13 7:06 ` Junio C Hamano
2006-01-13 19:12 ` Joel Becker
2006-01-13 19:39 ` Junio C Hamano
2006-01-13 20:01 ` Joel Becker
2006-01-13 20:33 ` Junio C Hamano
2006-01-13 20:46 ` Junio C Hamano
2006-01-13 21:47 ` Johannes Schindelin
2006-01-12 20:16 ` Alex Riesen
[not found] ` <20060112214642.3c88282c.seanlkml@sympatico.ca>
2006-01-13 2:46 ` sean
2006-01-13 3:58 ` Junio C Hamano
[not found] ` <20060112225800.411a04c1.seanlkml@sympatico.ca>
2006-01-13 3:58 ` sean
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=BAYC1-PASMTP117A18814EAAFACFE0F31DAE270@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--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).