From: Eric Wong <e@80x24.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] more archives of this list
Date: Sat, 6 Aug 2016 23:41:27 +0000 [thread overview]
Message-ID: <20160806234127.GA23580@starla> (raw)
In-Reply-To: <20160805202250.d23na5xdkmtnjgey@sigill.intra.peff.net>
Jeff King <peff@peff.net> wrote:
> Thanks. That's definitely an improvement. I still think the styling
> could go further, but I don't expect you to do it. It's something I may
> look into, but I should probably try to clear out my backlog of
> "to-review" patches before I go off spending time on it. :)
Heh, and I've nearly been sidetracked into hacking w3m to
iframes, persistent connections, color-mapping, etc, too :x
Right now, I'm just happy w3m supports piping buffers to
arbitrary programs (so one could run "git am" on the /raw
endpoint).
It'll be tough to beat a good local mail setup some of us have
with mutt/gnus. Being able to mark messages as read/unread
would either be intrusive (cookies/tracking users) or
cause accessibility problems (frames), I think...
...which is why the mbox.gz endpoints exist in public-inbox :>
So I think I'll try to do POP3 support, first...
next prev parent reply other threads:[~2016-08-06 23:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 0:48 [ANNOUNCE] more archives of this list Eric Wong
2016-07-10 3:47 ` Eric Wong
2016-07-28 20:59 ` Eric Wong
2016-08-05 9:28 ` Jeff King
2016-08-05 9:35 ` Jeff King
2016-08-05 9:59 ` Eric Wong
2016-08-05 18:19 ` Eric Wong
2016-08-05 20:22 ` Jeff King
2016-08-06 23:41 ` Eric Wong [this message]
2016-08-05 15:04 ` Duy Nguyen
2016-08-05 20:20 ` Jeff King
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=20160806234127.GA23580@starla \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).