From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] duplicated effort
Date: Tue, 24 Dec 2013 15:45:17 +0000 [thread overview]
Message-ID: <20131224154517.GB18259@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20131124103810.eklhad@comcast.net>
On Tue, Dec 24, 2013 at 10:38:10AM -0500, Karl Dahlke wrote:
> Ok guys, we are really screwing this up from the get-go.
> Chris and I are doing exactly the same work, but in two different branches.
Yeah, and I've just sent a number of patches which it sounds like aren't
needed/wanted against the master branch.
> I have confidence in us and wouldn't waste time and confusion with another branch.
> I don't understand branches anyways.
> I barely understand git!
> Besides, almost all the work is in two new files, jsdom.cpp and jsloc.cpp,
> which can't possibly screw up the original stuff.
> We only change the makefile at the last minute when it all works,
> or we're pretty sure it works.
The only comment I'd make on this is the typedef and constant changes have to be over multiple files
but I checked it builds (on debian against the libmozjs185 packages).
> I would recommend staying with the main branch and being very
> clear about who is going to do what.
> Anyways I guess I'll stop working on things until we know what we're doing.
Same here, appologies for the patch noise.
> But hey, don't get me wrong, I'd rather have lots of people trying to help
> than nobody trying to help.
Good to hear. These things take time to work out,
particularly when you have multiple developers working on a relatively small code base.
Cheers,
Adam.
prev parent reply other threads:[~2013-12-24 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 15:38 Karl Dahlke
2013-12-24 15:45 ` Adam Thompson [this message]
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=20131224154517.GB18259@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).