From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] tidy script bug workaround
Date: Sun, 13 Sep 2015 10:46:02 -0400 [thread overview]
Message-ID: <20150813104602.eklhad@comcast.net> (raw)
In-Reply-To: <87h9myu40p.fsf@mushroom.localdomain>
> I don't see anything obviously wrong, but yeah, it's tricky.
Ok, it's pushed, try it on your various examples.
> One of us should get on there, let them know about us, and see if we can
> get something to happen. I'm glad to do it unless someone else feels
> more diplomatic.
No one is more diplomatic than you.
Karl Dahlke
next prev parent reply other threads:[~2015-09-13 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 1:22 Karl Dahlke
2015-09-13 8:17 ` Chris Brannon
2015-09-13 14:46 ` Karl Dahlke [this message]
2015-09-13 16:37 ` Adam Thompson
2015-09-13 17:05 ` Karl Dahlke
2015-09-14 17:05 ` Adam Thompson
2015-09-14 18:37 ` Chris Brannon
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=20150813104602.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).