From: chris@the-brannons.com
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] [PATCH 1/2] Allow opening of existing files containing #
Date: Mon, 19 Dec 2011 12:55:48 -0600 [thread overview]
Message-ID: <87wr9sfl1n.fsf@the-brannons.com> (raw)
In-Reply-To: <1324304120-32208-1-git-send-email-tspivey@pcdesk.net> (Tyler Spivey's message of "Mon, 19 Dec 2011 06:15:19 -0800")
Tyler Spivey <tspivey@pcdesk.net> writes:
> If a filename contains # and already exists, edit it.
Yes, I like it! Both of these look good; I applied them locally. I'll
probably push later today.
Thank you for contributing,
-- Chris
prev parent reply other threads:[~2011-12-19 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 14:15 Tyler Spivey
2011-12-19 14:15 ` [Edbrowse-dev] [PATCH 2/2] Only check for sql if compiled in Tyler Spivey
2011-12-19 18:55 ` chris [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=87wr9sfl1n.fsf@the-brannons.com \
--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).