lkml.org 
[lkml]   [2007]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Patch 1/2] Trace code and documentation (updated)
Randy Dunlap wrote:
> On Wed, 19 Sep 2007 17:20:18 +0100 Christoph Hellwig wrote:
>
>> On Wed, Sep 19, 2007 at 07:14:47AM -0700, David Wilder wrote:
>>> I agree with you; however, this is in the example code in the
>>> Documentation directory, It is not part of the trace code. The example
>>> was just meant to be a demonstration of how the interface works.
>> So we tell people to write bad code? Wonderful..
>>
>> And while we're at it can we please stop the dumb idea to put example
>> code into Documentation? If example code doesn't get build during a
>> make oldconfig it will bitrot real fast and not be useful at all.
>
>
> That's why they exmaples should not be hidden/embedded in .txt files;
> they should be standalone .c files with makefiles etc.
>
> I've built and corrected several of them, but they would be more
> likely to be kept up-to-date if they are more available in standalone
> files.
>
> and they can be taken out of Documentation/ whenever they go into
> util-linux-ng or elsewhere. Let's get the order correct.
>
> ---
> ~Randy
>
IMHO keeping example code as standalone files under Documentation/* make
it easy to build an play with. I like it better than keeping it on some
project website where it is even less likely to maintained.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-09-19 19:45    [W:0.085 / U:1.312 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site