edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: edbrowse-dev <Edbrowse-dev@lists.the-brannons.com>
Subject: [Edbrowse-dev] release progress?
Date: Fri, 6 Jun 2014 09:07:33 +0100	[thread overview]
Message-ID: <20140606080733.GE2520@toaster.adamthompson.me.uk> (raw)

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

Hi all,

Now university's finally over (well unless anything's gone seriously wrong with
my final exams) I was wondering what needs to happen for the next release of
Edbrowse to be ready? I'm aware we're still awaiting a solution to the Debian
segfault issue, and was wondering if that was the only thing in the way?

Cheers,
Adam.

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

             reply	other threads:[~2014-06-06  8:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  8:07 Adam Thompson [this message]
2014-06-06  8:12 ` 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=20140606080733.GE2520@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --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).