From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (71-38-131-64.ptld.qwest.net [71.38.131.64]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 856D1789EC for ; Fri, 25 Sep 2015 13:52:23 -0700 (PDT) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20150824173812.eklhad@comcast.net> Date: Fri, 25 Sep 2015 13:55:35 -0700 In-Reply-To: <20150824173812.eklhad@comcast.net> (Karl Dahlke's message of "Thu, 24 Sep 2015 17:38:12 -0400") Message-ID: <87fv22kym0.fsf@mushroom.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] markdown X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 20:52:23 -0000 Karl Dahlke 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