From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>
Subject: [PATCH v2] devtools: make commits with stable tag outstanding
Date: Thu, 6 Apr 2017 14:33:41 +0800 [thread overview]
Message-ID: <1491460421-6597-1-git-send-email-yuanhan.liu@linux.intel.com> (raw)
In-Reply-To: <1487818172-12910-1-git-send-email-yuanhan.liu@linux.intel.com>
So that, as a stable maintainer while picking commits to a stable release,
I could pay less attention to those have it and pay more attention to those
don't have it.
Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
---
v2: - introduce a function stable_tag for that
- fix regexp
---
devtools/git-log-fixes.sh | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/devtools/git-log-fixes.sh b/devtools/git-log-fixes.sh
index d590735..359fbda 100755
--- a/devtools/git-log-fixes.sh
+++ b/devtools/git-log-fixes.sh
@@ -103,6 +103,16 @@ origin_version () # <origin_hash> ...
done | sort -uV | head -n1
}
+# print a marker for stable tag presense
+stable_tag () # <hash>
+{
+ if git log --format='%b' -1 $1 | grep -qi '^Cc: *stable@dpdk.org' ; then
+ echo 'S'
+ else
+ echo '-'
+ fi
+}
+
git log --oneline --reverse $range |
while read id headline ; do
origins=$(origin_filter $id)
@@ -116,5 +126,6 @@ while read id headline ; do
else
origver='N/A'
fi
- printf '%s %7s %s (%s)\n' $version $id "$headline" "$origver"
+ stable=$(stable_tag $id)
+ printf '%s %7s %s %s (%s)\n' $version $id $stable "$headline" "$origver"
done
--
1.9.0
next prev parent reply other threads:[~2017-04-06 6:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 2:49 [PATCH] devtools: make commits with stable tag outstanding Yuanhan Liu
2017-03-10 11:13 ` Thomas Monjalon
2017-04-06 6:31 ` Yuanhan Liu
2017-04-06 6:33 ` Yuanhan Liu [this message]
2017-04-06 19:25 ` [PATCH v2] " Thomas Monjalon
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=1491460421-6597-1-git-send-email-yuanhan.liu@linux.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.