From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] markdown
Date: Thu, 24 Sep 2015 17:38:12 -0400 [thread overview]
Message-ID: <20150824173812.eklhad@comcast.net> (raw)
Should explanatory text files, README CHANGES COPYING,
be rewritten in markdown?
It wouldn't be hard to do and they might render better
for outsiders coming to our project.
Should we scrap the todo file?
Nobody uses it, at all, I know I don't.
I just happen to notice that the first 5 or 6 paragraphs therein
are things we've done over the past couple months,
so if we're going to keep it then I should at least update it.
Karl Dahlke
next reply other threads:[~2015-09-24 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 21:38 Karl Dahlke [this message]
2015-09-25 20:55 ` Chris Brannon
2015-09-25 22:00 ` 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=20150824173812.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).