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] duplicated effort
Date: Tue, 24 Dec 2013 10:38:10 -0500	[thread overview]
Message-ID: <20131124103810.eklhad@comcast.net> (raw)

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.
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.
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.

But hey, don't get me wrong, I'd rather have lots of people trying to help
than nobody trying to help.

Karl Dahlke

             reply	other threads:[~2013-12-24 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24 15:38 Karl Dahlke [this message]
2013-12-24 15:45 ` 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=20131124103810.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).