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]  js progress update
Date: Wed, 08 Jan 2014 06:05:51 -0500	[thread overview]
Message-ID: <20140008060551.eklhad@comcast.net> (raw)

> so I can check if this is an edbrowse issue or a libmozjs24d debian package issue.

I would contact Jean, who contacted me in the first place.
He wants edbrowse in debian, and discovered the problem building against moz26.
He may know how those libraries are built and packaged etc.
He is French, but his English is perfect!

mengualjeanphi@free.fr

Karl Dahlke

             reply	other threads:[~2014-01-08 11:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 11:05 Karl Dahlke [this message]
2014-01-08 12:40 ` Adam Thompson
2014-01-14 20:43   ` Chris Brannon
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=20140008060551.eklhad@comcast.net \
    --to=eklhad@comcast.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).