From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Thu, 22 Jun 2017 10:13:49 +0200 Subject: [Buildroot] [PATCH 2/4 v2] tools: move test-pkg out of support/scripts In-Reply-To: <478f2e89-6356-48a7-f1c2-85c3bb6c7134@mind.be> References: <937e234aa28d4d11f676ce0c1437d2883cdd0f10.1497794488.git.yann.morin.1998@free.fr> <20170618161243.04768757@windsurf> <478f2e89-6356-48a7-f1c2-85c3bb6c7134@mind.be> Message-ID: <20170622101349.39793d32@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Thu, 22 Jun 2017 09:57:36 +0200, Arnout Vandecappelle wrote: > > No strong opinion on whether such a move is desirable, but at the very > > list I believe we should not add this 00-README.txt file. Nowhere else > > in the tree we have files named like this, and I don't think we should > > start adding these. > > Well, we have readme.txt in boards/, we have a README at the top level, we have > a README generated by legal-info, we have a readme.txt in checkpackagelib... We > indeed don't have a 00-README.txt though. IMO all of these files should be > called README.md (or readme.md) so they are nicely formatted when viewed online. > > For this particular instance, I do like having some kind of README there. We > need an overview of the existing tools somewhere, and I think a README file is a > more appropriate place than the manual because it's easier to keep consistent. > From the manual you can point to the directory. ACK, but then, named "readme.txt", to match what we're doing elsewhere: $ find . -name 'readme.txt' | wc -l 99 Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com