kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: ablacktshirt@gmail.com (Yubin Ruan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Efficient management of emails
Date: Mon, 15 Jan 2018 21:41:08 +0800	[thread overview]
Message-ID: <20180115134107.GA26707@HP> (raw)
In-Reply-To: <CAOfkYf6dwa-rpBiuAkDQPqNt=Dk3ed+T=tkHPhXpVZFGmq8acw@mail.gmail.com>

On Mon, Jan 15, 2018 at 06:04:54PM +0530, Shyam Saini wrote:
> Hi Everyone,
> 
> I have subscribed multiple mailing lists.
> 
> My question is  how do kernel developers and other users manage their
> emails on daily basis
> considering the fact that we receive hundreds of mails everyday.
> 
> One way is to tag each mails with their name for example "NetDev".
> 
> I'm curious is their any other way?
> 
> I would one really appreciate if someone will share their experience
> and use case.

Gmail allows you to filter emails and place them into corresponding mailbox.
For example, you can filter email by the "list" field and then tag them. For
emails sent to linux-kernel at vger.kernel.org, I tag them with the tag
"linux-kernel", and then Gmail will automatically create a folder (mailbox)
called "linux-kernel" and places all emails from that mailing list there. When
creating filter, you can also choose to remove those emails from INBOX so that
they will not appear in two mailbox. In this way, all mails from all mailing
list get sorted into different mailbox, making things clean.

And then I download them using offlineimap, and use mutt to view them.

        Yubin

  reply	other threads:[~2018-01-15 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15 12:34 Efficient management of emails Shyam Saini
2018-01-15 13:41 ` Yubin Ruan [this message]
2018-01-15 14:33   ` Yubin Ruan
2018-01-15 13:49 ` Greg KH
2018-01-15 20:20   ` valdis.kletnieks at vt.edu
2018-01-15 13:55 ` Steve Witt

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=20180115134107.GA26707@HP \
    --to=ablacktshirt@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).