From: Kevin Carhart <kevin@carhart.net>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] jdb redirect (fwd)
Date: Wed, 20 Sep 2017 17:02:20 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1709201700010.12844@carhart.net> (raw)
In-Reply-To: <87mv5qrqpd.fsf@prgmr.com>
Thanks, Chris! I'll be on my toes about that from now on. It makes
sense to have it shut off. I have not usually sent code that way or I may
have encountered it before.
>
> I wouldn't be surprised if the list was dropping attachments.
prev parent reply other threads:[~2017-09-21 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 0:16 Kevin Carhart
2017-09-20 3:31 ` Chris Brannon
2017-09-21 0:02 ` Kevin Carhart [this message]
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=alpine.LRH.2.03.1709201700010.12844@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=chris@the-brannons.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;
as well as URLs for NNTP newsgroup(s).