From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] status and suggest
Date: Tue, 24 Dec 2013 09:11:36 -0800 [thread overview]
Message-ID: <87txdy9nsn.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20131124115257.eklhad@comcast.net> (Karl Dahlke's message of "Tue, 24 Dec 2013 11:52:57 -0500")
Karl Dahlke <eklhad@comcast.net> writes:
> We let Adam move forward, and post patches,
> as he has been doing,
> chris and I review,
> and I push the patches with any possible changes.
Sounds good to me!
-- Chris
prev parent reply other threads:[~2013-12-24 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 16:52 Karl Dahlke
2013-12-24 17:11 ` Chris Brannon [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=87txdy9nsn.fsf@mushroom.PK5001Z \
--to=chris@the-brannons.com \
--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).