From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: users@linux.kernel.org, tools@linux.kernel.org
Subject: Gmail message ID finder Chrome extension
Date: Fri, 27 Mar 2020 12:54:02 -0400 [thread overview]
Message-ID: <20200327165402.slc5l46hc7hlo2l5@chatter.i7.local> (raw)
If you're a Chrome and Gmail user, you can try the following extension
to easily get the message-id of an email without having to "show
original" and hunting for the right header:
https://chrome.google.com/webstore/detail/gmail-message-id-finder/comcoiiifldaaejpbgbincdkoohihbae
The message-id will be copied to the clipboard with the "rfc822msgid:"
lead, but current versions of b4 will handle that properly.
I haven't been able to find something similar for Firefox, but perhaps
this is easy to do with a greasemonkey/tampermonkey extension.
Best regards,
-K
next reply other threads:[~2020-03-27 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 16:54 Konstantin Ryabitsev [this message]
2020-03-28 2:07 ` [kernel.org users] Gmail message ID finder Chrome extension Jason A. Donenfeld
2020-03-29 14:54 ` Linus Walleij
2020-03-29 17:13 ` Konstantin Ryabitsev
2020-03-30 20:31 ` Linus Walleij
2020-03-31 8:03 ` Geert Uytterhoeven
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=20200327165402.slc5l46hc7hlo2l5@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.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: link
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;
as well as URLs for NNTP newsgroup(s).