From: Michael Ellerman <firstname.lastname@example.org> To: Konstantin Ryabitsev <email@example.com> Cc: Benjamin Herrenschmidt <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, Christophe Leroy <email@example.com>, firstname.lastname@example.org, Paul Mackerras <email@example.com>, Eric Paris <firstname.lastname@example.org>, email@example.com Subject: Re: [PATCH v2 RESEND] powerpc/audit: Convert powerpc to AUDIT_ARCH_COMPAT_GENERIC Date: Thu, 04 Nov 2021 17:20:18 +1100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Konstantin Ryabitsev <firstname.lastname@example.org> writes: > On Wed, Nov 03, 2021 at 10:18:57AM +1100, Michael Ellerman wrote: >> It's not in next, that notification is from the b4 thanks script, which >> didn't notice that the commit has since been reverted. > > Yeah... I'm not sure how to catch that, but I'm open to suggestions. I think that's probably the first time I've had a commit and a revert of the commit in the same batch of thanks mails. And the notification is not wrong, the commit was applied with that SHA, it is in the tree. So I'm not sure it's very common to have a commit & a revert in the tree at the same time. On the other hand being able to generate a mail for an arbitrary revert would be helpful, ie. independent of any thanks state. eg, picking a random commit from the past: e95ad5f21693 ("powerpc/head_check: Fix shellcheck errors") If I revert that in my tree today, it'd be cool if I could run something that would detect the revert, backtrack to the reverted commit, extract the message-id from the Link: tag, and generate a reply to the original submission noting that it's now been reverted. In fact we could write a bot to do that across all commits ever ... cheers -- Linux-audit mailing list Linuxemail@example.com https://listman.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2021-11-04 13:19 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-24 13:36 Christophe Leroy 2021-08-24 14:47 ` Paul Moore 2021-08-24 17:11 ` Christophe Leroy 2021-08-24 23:01 ` Paul Moore 2021-08-26 14:37 ` Michael Ellerman 2021-08-27 0:52 ` Paul Moore 2021-11-02 10:11 ` Michael Ellerman 2021-11-02 13:01 ` Paul Moore 2021-11-02 23:18 ` Michael Ellerman 2021-11-02 23:54 ` Konstantin Ryabitsev 2021-11-04 6:20 ` Michael Ellerman [this message] 2021-11-04 14:32 ` Paul Moore 2021-11-03 1:15 ` Paul Moore 2021-11-02 23:17 ` Michael Ellerman
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v2 RESEND] powerpc/audit: Convert powerpc to AUDIT_ARCH_COMPAT_GENERIC' \ /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
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 NNTP newsgroup(s).