On Wed, Mar 11, 2015 at 12:31 AM, Jeff King <p...@peff.net> wrote: > On Tue, Mar 10, 2015 at 07:36:34PM -0700, Junio C Hamano wrote: > >> > Or if that would make the release notes too cumbersome to review, what >> > about using systemd's method? systemd's release notes include a >> > "contributions from" section at the very end that lists everyone with >> > a patch included in the release. >> >> 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. 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
