From: "Martin Ågren" <firstname.lastname@example.org> To: Junio C Hamano <email@example.com> Cc: Jeff King <firstname.lastname@example.org>, Git Mailing List <email@example.com> Subject: Re: [PATCH] Update .mailmap Date: Wed, 5 Aug 2020 08:53:41 +0200 [thread overview] Message-ID: <CAN0heSp+yf5jg0eNxGQXYUf2Y48nOuK-H3TX-y-Yc-TuzhOzuA@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Wed, 5 Aug 2020 at 00:01, Junio C Hamano <email@example.com> wrote: > > Jeff King <firstname.lastname@example.org> writes: > > > On Tue, Aug 04, 2020 at 11:07:58PM +0200, Martin Ågren wrote: > > > >> Similar to a35b13fce0 ("Update .mailmap", 2018-11-09), make the output > >> of `git shortlog -nse v2.10.0..master` duplicate-free by taking/guessing > >> the current and preferred addresses for authors that appear with more > >> than one address. > > > > I don't have any specific objections, but you might want to cc all of > > the impacted people, which would make them more likely to notice if this > > isn't the right thing to do. > > Excellent suggestion. > > A commit with 10 acked-by would be ideal, but at least let's make > sure we made enough effort to make them aware of, and asked them to > help make these entries correct. Thanks, both. I even kept adding to a list of the addresses in Cc form, but in the last second I bailed on adding a long-ish Cc list. Resend on its way. Martin
next prev parent reply other threads:[~2020-08-05 6:54 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-04 21:07 Martin Ågren 2020-08-04 21:28 ` Jeff King 2020-08-04 22:01 ` Junio C Hamano 2020-08-05 6:53 ` Martin Ågren [this message] 2020-08-05 6:54 ` [PATCH RESEND] " Martin Ågren 2020-08-05 7:00 ` Andreas Schwab 2020-08-05 7:09 ` Martin Ågren 2020-08-05 16:12 ` Junio C Hamano 2020-08-08 9:11 ` Damien Robert 2020-08-09 22:38 ` Ed Maste 2020-08-16 15:30 ` [PATCH v2] " Martin Ågren 2020-08-16 17:17 ` Junio C Hamano
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAN0heSp+yf5jg0eNxGQXYUf2Y48nOuK-H3TX-y-Yc-TuzhOzuA@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] Update .mailmap' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).