From: "Richard Yao" <ryao@gentoo.org> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] proj/genkernel:ryao commit in: / Date: Sun, 9 Jun 2013 08:32:20 +0000 (UTC) [thread overview] Message-ID: <1370762176.e9a12c3259f26966a2348f1dd45ceed3d16e8e42.ryao@gentoo> (raw) commit: e9a12c3259f26966a2348f1dd45ceed3d16e8e42 Author: Richard Yao <ryao <AT> gentoo <DOT> org> AuthorDate: Thu Jun 6 06:07:48 2013 +0000 Commit: Richard Yao <ryao <AT> gentoo <DOT> org> CommitDate: Sun Jun 9 07:16:16 2013 +0000 URL: http://git.overlays.gentoo.org/gitweb/?p=proj/genkernel.git;a=commit;h=e9a12c32 Update HACKING to use git-shortlog The old command we used to generate a change history for announcement emails no longer works, so we switch to git-shortlog. Signed-off-by: Richard Yao <ryao <AT> gentoo.org> --- HACKING | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/HACKING b/HACKING index 7ac0a60..d8b9f21 100644 --- a/HACKING +++ b/HACKING @@ -35,7 +35,7 @@ Rolling a release: <gentoo-genkernel@lists.gentoo.org> and <genkernel@gentoo.org>. Use - PREV_TAG=$(git tag -l | tail -n 2 | head -n 1) - git diff ${PREV_TAG}..v${PV} ChangeLog | /bin/grep '^+\($\| \)' | sed 's|^+ *||' | xsel + PREV_TAG=$(git tag -l | tail -n 2 | head -n 1) \ + git shortlog ${PREV_TAG}..v${PV} | xsel to generate the mail body.
WARNING: multiple messages have this Message-ID (diff)
From: "Richard Yao" <ryao@gentoo.org> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] proj/genkernel:master commit in: / Date: Sun, 9 Jun 2013 08:31:05 +0000 (UTC) [thread overview] Message-ID: <1370762176.e9a12c3259f26966a2348f1dd45ceed3d16e8e42.ryao@gentoo> (raw) Message-ID: <20130609083105.a9hM5qt97-HTTM2vAYh2cPmIh-MBKP-OMPw-YyGVJgs@z> (raw) commit: e9a12c3259f26966a2348f1dd45ceed3d16e8e42 Author: Richard Yao <ryao <AT> gentoo <DOT> org> AuthorDate: Thu Jun 6 06:07:48 2013 +0000 Commit: Richard Yao <ryao <AT> gentoo <DOT> org> CommitDate: Sun Jun 9 07:16:16 2013 +0000 URL: http://git.overlays.gentoo.org/gitweb/?p=proj/genkernel.git;a=commit;h=e9a12c32 Update HACKING to use git-shortlog The old command we used to generate a change history for announcement emails no longer works, so we switch to git-shortlog. Signed-off-by: Richard Yao <ryao <AT> gentoo.org> --- HACKING | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/HACKING b/HACKING index 7ac0a60..d8b9f21 100644 --- a/HACKING +++ b/HACKING @@ -35,7 +35,7 @@ Rolling a release: <gentoo-genkernel@lists.gentoo.org> and <genkernel@gentoo.org>. Use - PREV_TAG=$(git tag -l | tail -n 2 | head -n 1) - git diff ${PREV_TAG}..v${PV} ChangeLog | /bin/grep '^+\($\| \)' | sed 's|^+ *||' | xsel + PREV_TAG=$(git tag -l | tail -n 2 | head -n 1) \ + git shortlog ${PREV_TAG}..v${PV} | xsel to generate the mail body.
next reply other threads:[~2013-06-09 8:32 UTC|newest] Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-09 8:32 Richard Yao [this message] 2013-06-09 8:31 ` [gentoo-commits] proj/genkernel:master commit in: / Richard Yao -- strict thread matches above, loose matches on Subject: below -- 2013-10-02 12:43 [gentoo-commits] proj/genkernel:ryao " Richard Yao 2013-10-02 12:43 Richard Yao 2013-10-02 12:43 Richard Yao 2013-06-09 13:57 Richard Yao 2013-06-09 13:57 [gentoo-commits] proj/genkernel:master " Richard Yao 2013-06-09 13:57 ` [gentoo-commits] proj/genkernel:ryao " Richard Yao 2013-06-09 13:57 Richard Yao 2013-06-09 13:33 Richard Yao 2013-06-09 13:33 Richard Yao 2013-06-09 13:17 Richard Yao 2013-06-09 13:17 Richard Yao 2013-06-09 10:05 Richard Yao 2013-06-09 10:05 Richard Yao 2013-06-09 10:02 Richard Yao 2013-06-09 10:02 Richard Yao 2013-06-09 9:58 Richard Yao 2013-06-09 9:58 Richard Yao 2013-06-09 9:57 Richard Yao 2013-06-09 9:53 Richard Yao 2013-06-09 9:51 Richard Yao 2013-06-09 9:49 Richard Yao 2013-06-09 8:32 Richard Yao 2013-06-09 8:32 Richard Yao 2013-06-09 8:32 Richard Yao 2013-06-09 8:32 Richard Yao 2013-06-09 8:16 Richard Yao 2013-06-09 7:58 Richard Yao 2013-06-09 6:43 Richard Yao 2013-06-06 6:09 Richard Yao 2013-06-06 5:57 Richard Yao 2013-06-06 5:54 Richard Yao 2013-06-06 3:52 Richard Yao 2013-06-06 3:36 Richard Yao 2013-06-06 3:36 Richard Yao 2013-06-06 3:36 Richard Yao 2013-06-06 3:36 Richard Yao 2013-06-03 23:49 [gentoo-commits] proj/genkernel:master " Richard Yao 2013-06-06 3:36 ` [gentoo-commits] proj/genkernel:ryao " Richard Yao 2013-06-03 23:49 Richard Yao 2013-06-03 23:47 Richard Yao 2013-06-03 23:43 Richard Yao 2013-06-03 23:35 Richard Yao 2013-06-03 23:34 Richard Yao 2013-06-03 23:34 Richard Yao 2012-11-11 18:04 Richard Yao 2012-11-11 17:32 Richard Yao 2012-11-05 18:42 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-11-05 18:30 Richard Yao 2012-08-25 1:44 Richard Yao 2012-08-25 1:36 Richard Yao 2012-08-25 1:19 Richard Yao 2012-08-25 1:04 Richard Yao 2012-08-16 18:33 Richard Yao 2012-08-16 18:33 Richard Yao 2012-08-16 18:33 Richard Yao
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=1370762176.e9a12c3259f26966a2348f1dd45ceed3d16e8e42.ryao@gentoo \ --to=ryao@gentoo.org \ --cc=gentoo-commits@lists.gentoo.org \ --cc=gentoo-dev@lists.gentoo.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: linkBe 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