edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Kevin Carhart <kevin@carhart.net>
Cc: Karl Dahlke <eklhad@comcast.net>, Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] js abort on db5
Date: Thu, 12 Jan 2017 18:38:35 +0000	[thread overview]
Message-ID: <20170112183835.GB28637@odin> (raw)
In-Reply-To: <alpine.LRH.2.03.1612281932060.4769@carhart.net>

[-- Attachment #1: Type: text/plain, Size: 284 bytes --]

On Wed, Dec 28, 2016 at 07:32:32PM -0800, Kevin Carhart wrote:
> >If you were running js, with debug 5, and js is done, it's hard to see why you would want to march on. You can't even run jdb any more.
> 
> Exactly.

Yeah, let's do this.  It'd make things a bit easier I think.

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-01-12 18:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29  2:30 Kevin Carhart
2016-12-29  3:29 ` Karl Dahlke
2016-12-29  3:32   ` Kevin Carhart
2017-01-12 18:38     ` Adam Thompson [this message]
2017-01-12 18:56       ` Karl Dahlke
2016-12-29  4:19   ` 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=20170112183835.GB28637@odin \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    --cc=kevin@carhart.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).