From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Those header tags, fabulous!
Date: Fri, 23 Feb 2018 16:46:37 -0500 [thread overview]
Message-ID: <20180123164637.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1802231616500.2638@debian.pulsar.com>
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
Well it's a little embarrasing, because folks have been asking for them for years, and it was really easy to do, so I should have done it sooner. Sorry.
This will be part of 3.7.3 however, we already stamped 3.7.2.
But if they are really useful, and we get a couple more useful things in quickly, like gopher, we can always release 3.7.2.1.
I mean it's our ballgame, isn't it?
Karl Dahlke
prev parent reply other threads:[~2018-02-23 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 21:20 Chuck Hallenbeck
2018-02-23 21:46 ` Karl Dahlke [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=20180123164637.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@lists.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).