edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] ?
Date: Sun, 30 Aug 2015 18:10:58 -0700	[thread overview]
Message-ID: <20150730181058.kevin@carhart.net > (raw)

Here's something:
I couldn't tell when I had a message with extra lines with just
a literal question mark, since I mistook it for an edbrowse ?

Kevin

             reply	other threads:[~2015-08-31  1:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  1:10 Kevin Carhart [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-27  5:20 [Edbrowse-dev] == Kevin Carhart
2015-01-07  8:49 [Edbrowse-dev] & Karl Dahlke
2015-01-06 22:27 Karl Dahlke
2015-01-07  8:27 ` Adam Thompson
2015-01-06  2:19 Karl Dahlke
2015-01-06 21:29 ` 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='20150730181058.kevin@carhart.net ' \
    --to=kevin@carhart.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).