From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Javascript support
Date: Tue, 24 Dec 2013 09:25:14 +0000 [thread overview]
Message-ID: <20131224092514.GE16257@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <87bo07d4nq.fsf@mushroom.PK5001Z>
On Mon, Dec 23, 2013 at 06:26:49AM -0800, Chris Brannon wrote:
> How familiar are you with git? If you aren't, I'll write up a
> long-winded explanation. Here's the short form.
> Use git send-email to send your patches to this list.
> You might want to run the following from the root of your edbrowse
> repository:
> git config --replace sendemail.to 'edbrowse-dev@lists.the-brannons.com'
I'm not massively familiar with git,
but I do know distributed version control and how to commit changes to my local repository.
Thanks for the tip about git config though, that's a git thing which I was not aware of.
> Also, please insure that your code is formatted with tools/ebindent from
> the edbrowse repo, just to be consistent with the rest of the codebase.
I'll try. As long as there's not too much c++ weirdness in the code, indent
should cope relatively well I think.
Cheers,
Adam.
next prev parent reply other threads:[~2013-12-24 9:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 22:26 Karl Dahlke
2013-12-23 9:26 ` Adam Thompson
2013-12-23 14:26 ` Chris Brannon
2013-12-24 9:25 ` Adam Thompson [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-23 14:29 Karl Dahlke
2013-12-18 18:45 [Edbrowse-dev] html unicode translations in edbrowse Karl Dahlke
2013-12-21 18:00 ` [Edbrowse-dev] Javascript support MENGUAL Jean-Philippe
2013-12-22 15:42 ` Chris Brannon
2013-12-22 16:48 ` Adam Thompson
2013-12-22 18:36 ` Chris Brannon
2013-12-22 19:10 ` Adam Thompson
2014-01-08 12:50 ` 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=20131224092514.GE16257@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=chris@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).