Re: Sparse documentation format, rST vs MD

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Aug 07, 2017 at 07:46:25AM -0400, Christopher Li wrote:
> On Mon, Aug 7, 2017 at 12:56 AM, Josh Triplett <josh@xxxxxxxxxxxxxxxx> wrote:
> 
> > I personally find the Markdown format *much* closer to normal text
> 
> Same here. But I know I am biased.
> 
> > formatting in email, and I'd highly recommend using it.  I'm not sure
> > why the kernel picked reStructuredText, but I don't think there's likely
> > to be a huge amount of cross-pollination between the two in terms of
> > documentation.  In particular, you're unlikely to want to borrow files
> > from the kernel given the different license.
> 
> Mostly just submitting-patches.rst for the Signed-off-by part.
> For the coding style we can just point to the Linux kernel one.
> 
> I think it is fine to have a few *documents* remain GPL in sparse.
> It is not link to any source file. It is not a source file at all.
> I don't think any one will nick pick the license detail on this.

Purely procedural documentation seems fine, sure.
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux