From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Finding cycles in the tree
Date: Sat, 28 Jan 2017 18:24:51 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1701281821060.32204@carhart.net> (raw)
In-Reply-To: <20170027050941.eklhad@comcast.net>
On Fri, 27 Jan 2017, Karl Dahlke wrote:
>> What do you think about trying to isolate the cause by going into the
>
> I don't think it would tell us anything. This problem popped up because
> we got enough of the js working to move forward, and make the links,
> hopefully correct.) It's like turning on the light and seeing the mess.
Ahh yes, I take your point on that. This has happened to me quite a bit.
You pore over problem 1, fix it, and CONGRATULATIONS! Your reward is.....
........ problem 2! A bigger mess. So it's a good thing, it just
doesn't feel like one. You have to bear in mind that the whole thing was
masked out up until that point and you have now revealed it, not just get
frustrated by problem 2.
prev parent reply other threads:[~2017-01-29 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 2:19 Karl Dahlke
2017-01-27 6:29 ` Kevin Carhart
2017-01-27 6:37 ` Kevin Carhart
2017-01-27 10:09 ` Karl Dahlke
2017-01-29 2:24 ` Kevin Carhart [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=alpine.LRH.2.03.1701281821060.32204@carhart.net \
--to=kevin@carhart.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).