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] patch
Date: Tue, 24 Dec 2013 14:40:28 -0500	[thread overview]
Message-ID: <20131124144028.eklhad@comcast.net> (raw)

> We really need to work out a better way for patch submission.
> If I can work out how to use github I could probably do something fancy like
> fork the repo and push to my copy or something like that.

I don't think that would be any better / easier.
The only way that is probably better is if Chris gives you write access,
then you could make your changes, test them, commit, and push,
without going around the circle through us and then pull and compare.
That's ok with me, especially since you are now entirely inside two files
that aren't even used in the primary build.
Or you could just work locally with *.cpp,
take a week or two or three or whatever it takes,
then send me one big patch at the end that says
Hey it works with the c++ interface.
Either way is ok with me.
Either way it's a nice Christmas present.

Karl Dahlke

             reply	other threads:[~2013-12-24 19:40 UTC|newest]

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