From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] <object>
Date: Sat, 16 Jan 2016 23:17:19 -0800 [thread overview]
Message-ID: <87ziw44qv4.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20160015180637.eklhad@comcast.net> (Karl Dahlke's message of "Fri, 15 Jan 2016 18:06:37 -0500")
Karl Dahlke <eklhad@comcast.net> writes:
> Speaking of object tags, should I try to slide a minimal understanding
> of object into 3.6.1?
Sounds cool. We really do want to know what is inside of those at
least.
-- Chris
prev parent reply other threads:[~2016-01-17 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 23:06 Karl Dahlke
2016-01-16 14:39 ` Adam Thompson
2016-01-17 7:00 ` Karl Dahlke
2016-01-17 7:17 ` Chris Brannon [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=87ziw44qv4.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--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).