Re: and that would be it for kerneldoc fixes

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

 



On 08/28/2012 04:12 AM, Robert P. J. Day wrote:
> On Mon, 27 Aug 2012, Rob Landley wrote:
> 
>> On 08/26/2012 07:31 AM, Robert P. J. Day wrote:
> 
>>>   i hope these were in acceptable format and while i understand
>>> it's a bit late in the cycle to try to add doc fixes, it would be
>>> just ducky if these could be pushed since they clearly don't
>>> affect functionality and will get rid of a *pile* of annoying
>>> warnings.
>>
>> I'll see what I can do,
> 
>   at this point, i've either submitted patches for stuff that
> generates warnings, or sent private emails to the people responsible
> for the kerneldoc content that does, so almost all of the warnings
> have been "addressed" in some way; now to wait while the fixes trickle
> in.
> 
>   i apologize for my sudden obsession in cleaning this stuff up, but i
> really want to promote some of these docs to my students and i want to
> minimize the annoying warnings they have to see.
> 
>   onward...

I'm all for it.  I would love to take advantage of it.

It's just that when Documentation/ was first handed over I devoted a
weekend to getting my kernel.org account reset (after last year's
break-in disabled everything and introduced a new layer of bureaucracy),
and at the end of it had made exactly zero progress. They switched from
providing shell access to some handcrafted git-only filter that
prevented me from updating kernel.org/doc, and I needed a pgp key with
signatures from people with existing kernel.org accounts (people listed
in MAINTAINERS wasn't good enough), when the last in-person event I
attended was 2010.

This is _my_ problem not yours, and since then I've made some progress
on it. It's just... got me off to a slow start. To be honest, I've been
funneling stuff through trivial@xxxxxxxxxx since the nice maintainer
there was kind enough to host things in a way Linus will pull. But the
big cleanups (collating the translations under a common directory,
collating the architectures under a common directory) require me to have
a git tree with the appropriate magic blessing sucked into linux-next, so...

> rday

Rob
-- 
GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code.
Either it's "mere aggregation", or a license violation.  Pick one.
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux