From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] markdown
Date: Fri, 25 Sep 2015 13:55:35 -0700 [thread overview]
Message-ID: <87fv22kym0.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20150824173812.eklhad@comcast.net> (Karl Dahlke's message of "Thu, 24 Sep 2015 17:38:12 -0400")
Karl Dahlke <eklhad@comcast.net> writes:
> Should explanatory text files, README CHANGES COPYING,
> be rewritten in markdown?
I don't know, because I'm not sure how these things render for everyone
else when browsing from github. Perhaps the most important one is
README. Maybe that should be rewritten and renamed to README.md?
> Should we scrap the todo file?
We can probably scrap it. We all know what the priorities are, and
we're making progress on those fronts.
Maybe sometime in the future github's issue tracker will work well with
edbrowse also.
We can always resurrect it if need be.
-- Chris
next prev parent reply other threads:[~2015-09-25 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 21:38 Karl Dahlke
2015-09-25 20:55 ` Chris Brannon [this message]
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=87fv22kym0.fsf@mushroom.localdomain \
--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).