From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] js progress update
Date: Tue, 14 Jan 2014 12:43:32 -0800 [thread overview]
Message-ID: <87y52iuwej.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140108124047.GB3935@toaster.adamthompson.me.uk> (Adam Thompson's message of "Wed, 8 Jan 2014 12:40:47 +0000")
Adam Thompson <arthompson1990@gmail.com> writes:
> Thanks, will do. Whilst I do this, is there any chance people could test my
> fork of edbrowse as well?
Sorry, I had a bit of a rough week, so I haven't really had a chance to
look at this. It builds for me. I'll try and test and review in the
next couple of days.
Thanks,
-- Chris
next prev parent reply other threads:[~2014-01-14 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 11:05 Karl Dahlke
2014-01-08 12:40 ` Adam Thompson
2014-01-14 20:43 ` Chris Brannon [this message]
2014-01-14 21:27 ` Adam Thompson
2014-01-14 22:17 ` Chris Brannon
2014-01-17 12:09 ` Adam Thompson
2014-01-17 18:42 ` Chris Brannon
-- strict thread matches above, loose matches on Subject: below --
2014-01-07 12:08 Adam Thompson
2014-01-07 12:10 ` [Edbrowse-dev] js progress update1 Adam Thompson
2014-01-08 10:03 ` [Edbrowse-dev] js progress update 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:
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=87y52iuwej.fsf@mushroom.PK5001Z \
--to=chris@the-brannons.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).