From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: "email bankruptcy"? [was: RFE: default hooks for git repositories]
Date: Tue, 2 Apr 2019 08:00:42 +0000 [thread overview]
Message-ID: <20190402080042.2n53qa62yzjanxgu@dcvr> (raw)
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Sorry, Eric, I'm close to declaring email bankruptcy. :)
Btw, I'm still trying to grasp exactly the meaning of that line...
Does that mean you're not getting enough email? :>
Anyways; feel free to elaborate if there's something along
the lines of public-inbox that might help with your own mail...
(Perhaps along the lines of
https://public-inbox.org/meta/20190313000700.5paqmd43escrydpg@dcvr/
("public-inbox for individual mail") and/or something along
the lines of a mairix/notmuch workalike, locally)
reply other threads:[~2019-04-02 8:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190402080042.2n53qa62yzjanxgu@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).