From: Jeff King <peff@peff•net>
To: Junio C Hamano <gitster@pobox•com>
Cc: "Jason St. John" <jstjohn@purdue•edu>,
Christian Couder <christian.couder@gmail•com>,
Michael J Gruber <git@drmicha•warpmail.net>,
David Kastrup <dak@gnu•org>, git <git@vger•kernel.org>
Subject: Re: Promoting Git developers
Date: Wed, 11 Mar 2015 03:54:29 -0400 [thread overview]
Message-ID: <20150311075429.GA10300@peff.net> (raw)
In-Reply-To: <CAPc5daUVVk+SYgwCj9JftzXgV7=9kPprdBPCWHS5XQOa5uF69Q@mail.gmail.com>
On Wed, Mar 11, 2015 at 12:38:21AM -0700, Junio C Hamano wrote:
> >> I can add "shortlog --no-merges -s -n v2.3.0..v2.4.0" at the end of
> >> the e-mail when the release notes is sent out. That might be a good
> >> enough balance between the usefulness of the release notes to its
> >> customers and giving credits to individuals in a way a bit more
> >> visible than "if you are interested, run shortlog yourself" [*4*].
> >
> > I somehow thought you already did this, but it looks like you just do
> > shortlog (without the "-ns") for the "maint" release announcement.
>
> That is because (a) it is scripted in Meta/Announce, and (b) I strip it
> out for feature releases, as the plain shortlog output with full feature
> list is usually ends up being just too long for the announce message.
Yeah, I figured the length was the reason.
> Perhaps I'll add "shortlog -s | pr -3" or something at the end for both
> maintenance track and feature releases. Names only, unordered and
> hopefully not overly long.
Yes, I was thinking something along those lines. Maybe:
# example
old=v2.2.0
new=v2.3.0
# like "shortlog -s", but we do not even care about the numbers
shortlog () {
git log --format=%aN "$@" | sort -u
}
compact () {
perl -lne 'push @x, $_; END { print join(", ", @x) }' |
fold -s
}
count () {
shortlog $old..$new | wc -l
}
newbies () {
comm -23 <(shortlog $old..$new) <(shortlog $old) | compact
}
oldtimers () {
comm -12 <(shortlog $old..$new) <(shortlog $old) | compact
}
cat <<EOF
Git $new was developed with commits from $(count) people. Thanks very
much to our returning developers:
$(oldtimers)
and welcome to new contributors in this release:
$(newbies)
EOF
Or something along those lines. The wording and indentation of the
message could probably use tweaking. And there is a bash-ism in the
script. :)
-Peff
next prev parent reply other threads:[~2015-03-11 7:54 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 7:18 Promoting Git developers (was: Bashing freelancers) Christian Couder
2015-03-09 13:57 ` Michael J Gruber
2015-03-09 14:31 ` Promoting Git developers David Kastrup
2015-03-09 18:32 ` Philip Oakley
2015-03-10 7:45 ` Junio C Hamano
2015-03-10 11:51 ` Promoting Git developers (was: Bashing freelancers) Christian Couder
2015-03-10 17:23 ` Promoting Git developers Junio C Hamano
2015-03-11 1:04 ` Jason St. John
2015-03-11 2:13 ` Duy Nguyen
2015-03-11 4:16 ` Junio C Hamano
2015-03-12 2:15 ` Duy Nguyen
2015-03-12 4:53 ` Junio C Hamano
2015-03-12 7:45 ` Fredrik Gustafsson
2015-03-12 18:43 ` Junio C Hamano
2015-03-11 2:36 ` Junio C Hamano
2015-03-11 7:31 ` Jeff King
2015-03-11 7:38 ` Junio C Hamano
2015-03-11 7:54 ` Jeff King [this message]
2015-03-11 21:28 ` Junio C Hamano
2015-03-11 23:17 ` Andrew Ardill
2015-03-12 22:31 ` Jeff King
2015-03-12 22:36 ` Junio C Hamano
2015-03-12 22:43 ` Jeff King
2015-03-12 5:05 ` Junio C Hamano
2015-03-12 22:38 ` Jeff King
2015-03-12 22:58 ` Junio C Hamano
2015-03-15 9:12 ` Christian Couder
2015-03-11 13:53 ` Christian Couder
2015-03-11 20:42 ` Junio C Hamano
2015-03-15 8:46 ` Christian Couder
2015-03-15 22:18 ` Junio C Hamano
2015-03-15 22:43 ` Randall S. Becker
2015-03-16 9:10 ` Christian Couder
2015-03-16 9:20 ` David Kastrup
2015-03-16 17:06 ` Stefan Beller
2015-03-17 20:08 ` Christian Couder
2015-03-17 20:16 ` Junio C Hamano
2015-03-16 23:39 ` David Lang
2015-03-17 5:25 ` Junio C Hamano
2015-03-17 5:56 ` David Lang
2015-03-17 20:15 ` Christian Couder
2015-03-17 9:43 ` Thomas Ferris Nicolaisen
2015-03-17 19:51 ` Christian Couder
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=20150311075429.GA10300@peff.net \
--to=peff@peff$(echo .)net \
--cc=christian.couder@gmail$(echo .)com \
--cc=dak@gnu$(echo .)org \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=jstjohn@purdue$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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