From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@the-brannons.com
Subject: [Edbrowse-dev] tales from the front
Date: Thu, 24 Mar 2016 00:20:13 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1603232359030.15001@carhart.net> (raw)
In-Reply-To: <20160223211255.eklhad@comcast.net>
[ Karl said, that he can't read the messages in the thread about the 348
issue, probably because of the 348 issue itself. CCing the list just for
fun.]
> The great irony is, I can't read any messages in this thread,
> probably because of the 348 issue.
>
Hi Karl
Yes, those kinds of two-level things are real, and a big mess. I had a
job in eDiscovery, in other words, gathering documents in the discovery
phase of trials. So I'm scripting HTTP to gather hundreds of pages from
an intranet wiki, the topic of which ITSELF happens to be about software
engineering and web pages. There was absolutely no way to distinguish
things in markup that I was supposed to identify and switch on, versus
inline code examples written by engineers demonstrating concepts to each
other, and that happened to be of the same thing! I tried to tell my boss
what I was up against and didn't get too far.
parent reply other threads:[~2016-03-24 7:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20160223211255.eklhad@comcast.net>]
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.1603232359030.15001@carhart.net \
--to=kevin@carhart.net \
--cc=edbrowse-dev@the-brannons.com \
--cc=eklhad@comcast.net \
/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).