From: david@lang.hm
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Dave needs to get better at pushing out patches
Date: Thu, 8 Dec 2011 03:55:47 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1112080353040.2347@asgard.lang.hm> (raw)
In-Reply-To: <CAA93jw6ZN8XeLt9RjS_WFPcCVegpoX4TCJC+oY_aJQajuY5_BQ@mail.gmail.com>
On Thu, 8 Dec 2011, Dave Taht wrote:
> The overhead of formatting a patch properly is trivial.
>
> Getting a patch set into thunderbird or the web so totally dwarfs the
> tedium of actually creating the patch, it's unbelievable.
>
> I have a string of mostly trivial patches I could have got out ages
> ago with git send-email. I could slam out patches every day that way
> and be a zillion times more effective coding-wise.
>
> All year I have tried to get to where I could send email effectively
> from the command line on my laptop or wherever, and today's email
> server setups have become so complex that I have completely failed to
> find a way to so. (I note that I am frequently offline and need to be
> able to do it from my main development box, my laptop, and I have been
> highly mobile of late)
>
> I recently spent most of a day trying to get bufferbloat.net's email
> server to take email from me, using sasl, or certs, and failed
> entirely.
>
> I've been running my own email servers for 3 decades now, It's both
> embarrassing to me and unbelievable how difficult it's become to use
> such a basic transport.
>
> And I USED to read my email with emacs. I liked it. I was FAR more
> productive switching from code to irc to email to patches and back
> when I didn't have to run tools like a browser and thunderbird all the
> time.
as a holdout pine user I understand your frustration :-)
have you considered doing something like setting up openvpn to connect to
the bufferbloat.net server and then configuring the mail server to trust
mail arriving form the VPN clients?
I know this is horrible overkill for such a trivial job, but it avoids all
the problems of doing authentication for the SMTP connection (and the fact
that many locations block outbound connections from dhcp addresses to port
25)
David Lang
next prev parent reply other threads:[~2011-12-08 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 10:16 Dave Taht
2011-12-08 11:55 ` david [this message]
2011-12-08 12:06 ` Dave Taht
2011-12-08 12:18 ` david
2011-12-08 12:39 ` Dave Taht
2011-12-08 12:54 ` david
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://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1112080353040.2347@asgard.lang.hm \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cerowrt@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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