edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]    &
Date: Wed, 07 Jan 2015 03:49:35 -0500	[thread overview]
Message-ID: <20150007034935.eklhad@comcast.net> (raw)

> I'm trying to avoid having to fork mid-download and all the issues that causes.

Right. I'm going to let Chris have a look and see what he thinks.
May well be that we just stop the download, set some flags, fork the child,
and restart the download there.
For as rare as this is, I wouldn't have a problem with that.

Karl Dahlke

             reply	other threads:[~2015-01-07  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07  8:49 Karl Dahlke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-27  5:20 [Edbrowse-dev] == Kevin Carhart
2015-08-31  1:10 [Edbrowse-dev] ? Kevin Carhart
2015-01-06 22:27 [Edbrowse-dev] & Karl Dahlke
2015-01-07  8:27 ` Adam Thompson
2015-01-06  2:19 Karl Dahlke
2015-01-06 21:29 ` Adam Thompson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150007034935.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \


* 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).