From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] one more necessary big change
Date: Thu, 06 Feb 2014 10:36:52 -0500 [thread overview]
Message-ID: <20140106103652.eklhad@comcast.net> (raw)
Well I would call this a bug fix, not a big change,
but maybe that's just a subjective distinction.
If you mean things like jsloc.cpp
loc_toString()
line 94
jsval rval;
Making that and others rooted, then that's fine, go ahead and push
and I'll just look at the log diff later.
If it's something different then let us know.
Thanks.
Karl Dahlke
next reply other threads:[~2014-02-06 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 15:36 Karl Dahlke [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-06 15:14 Chris Brannon
2014-02-06 17:57 ` 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=20140106103652.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).