From: John Hendy <jw.hendy@gmail.com>
To: M <Elwood151@web.de>
Cc: emacs orgmode-mailinglist <Emacs-orgmode@gnu.org>
Subject: Re: (OT) How to follow a mailing list with very high activity (like this one here)?
Date: Thu, 17 Apr 2014 07:52:00 -0500 [thread overview]
Message-ID: <CA+M2ft9kbxv-dGy6vYLDaReZd+PmfUj_t7c7jjSO3Rp9Qaqecw@mail.gmail.com> (raw)
In-Reply-To: <CF74A68C.1C7DB%Elwood151@web.de>
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
On Apr 16, 2014 2:29 PM, "M" <Elwood151@web.de> wrote:
>
> This is off-topic, but I hope that someone can give me some good advice:
>
> During the last years, I'be become a real org-mode fan and I want to stay
> current and be active in the great org-mode community.
> I've subscribed to the orgmode mailinglist about 1,5 years ago and so I
have
> >17.500 mails in my inbox.
>
> You really have to be organized very well to deal with so much
information!
> Is there a tutorial somewhere for good approaches, how to participate
>
[snip]
I must be way simplistic on thus one. I just use gmail.
- if something sounds relevant or I possibly know anything about how to
help, I open the email. If I was wing about that judgement, I delete it.
- either way, from then on replies to that thread show up as flagged
important in gmail. For accidental openings, I generally remember the
ballpark title and delete follow ups. For relevant notes, I keep them in my
inbox until I can chime in to help or try the solution/trick myself. Then I
delete.
- if I missed something relevant and run into an issue, I Google the
problem and generally find the thread again.
- if I don't, the ML points in the right direction when I inquire, often
due to not knowing the syntax to Google my problem :)
For a very small set of things I want around for easy reference, I stick
then in an "org" label in gmail.
This replicates well between phone and browser, and my first step most
mornings is swiping away most emails from the list that came in overnight.
John
> Kind regards
>
> Martin
>
>
>
[-- Attachment #2: Type: text/html, Size: 1989 bytes --]
next prev parent reply other threads:[~2014-04-17 12:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 19:28 (OT) How to follow a mailing list with very high activity (like this one here)? M
2014-04-16 20:05 ` Alexander Baier
2014-04-16 21:10 ` Sacha Chua
2014-04-17 15:03 ` Igor Sosa Mayor
2014-04-17 23:56 ` Sacha Chua
2014-04-18 5:24 ` Igor Sosa Mayor
2014-04-17 7:38 ` Bastien
2014-04-17 9:10 ` Esben Stien
2014-04-17 12:52 ` John Hendy [this message]
2014-04-17 12:59 ` J. David Boyd
2014-04-17 13:40 ` Bastien
2014-04-17 14:28 ` John Hendy
2014-04-17 14:37 ` Bastien
2014-04-17 15:30 ` Eric S Fraga
2014-04-18 6:53 ` Alan Schmitt
2014-04-18 3:45 ` Brady Trainor
2014-04-18 8:35 ` Sharon Kimble
2014-05-30 5:38 ` Brady Trainor
2014-04-18 8:09 ` Martin Beck
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: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+M2ft9kbxv-dGy6vYLDaReZd+PmfUj_t7c7jjSO3Rp9Qaqecw@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=Elwood151@web.de \
--cc=Emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).