From: baggett@Colorado.EDU
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] Buffers issue
Date: Wed, 9 Jan 2019 11:38:41 -0700 (MST) [thread overview]
Message-ID: <alpine.LNX.2.20.1901091137010.575@Jackie> (raw)
I can't imagine a reason not to say yes.
This looks like a good defense against the website re-doers.
Larry
reply other threads:[~2019-01-09 18:46 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.20.1901091137010.575@Jackie \
--to=baggett@colorado.edu \
--cc=edbrowse-dev@edbrowse.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 NNTP newsgroup(s).