summaryrefslogtreecommitdiff
path: root/set-serial.sh
diff options
context:
space:
mode:
authorPeter Simons <simons@cryp.to>2010-01-12 23:01:16 +0100
committerPeter Simons <simons@cryp.to>2010-01-12 23:01:16 +0100
commitb3b1d7013c1f3b974574881befcd5f2aee7dd510 (patch)
treed07342a2073e301d1e4c47709f42ad34def5f866 /set-serial.sh
parent810f2a8cc3e9dc34ef68b123ab15aaf07648e702 (diff)
downloadautoconf-archive-b3b1d7013c1f3b974574881befcd5f2aee7dd510.tar.gz
set-serial.sh: use "git log --oneline" to determine the number of revision for a macro
This seems to be more reliable (and easier) than the previous 'grep -c' approach.
Diffstat (limited to 'set-serial.sh')
-rwxr-xr-xset-serial.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/set-serial.sh b/set-serial.sh
index fe9b442..08cbe24 100755
--- a/set-serial.sh
+++ b/set-serial.sh
@@ -14,7 +14,7 @@ set-serial-number()
for n in "$@"; do
echo "$n ... "
# Determine the number of revisions that have occurred to the macro.
- revision=$(git log -- "$n" | egrep -c '^commit [0-9a-f]')
+ revision=$(git log --oneline -- "$n" | wc -l)
# Update the serial number in the m4 file.
set-serial-number "$n" "$revision"
# Check whether git regards the file as "modified" now. If it does,