From: maximilian attems <janitor@sternwelten.at>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] patches: delete 75 unused files
Date: Fri, 10 Dec 2004 10:43:08 +0000 [thread overview]
Message-ID: <20041210104308.GC2211@stro.at> (raw)
In-Reply-To: <20041208155439.GC31550@nd47.coderock.org>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
On Thu, 09 Dec 2004, Gustavo Franco wrote:
> On Wed, 2004-12-08 at 17:15 -0500, Jim Nelson wrote:
> > [...]
> > >
> > > Yes, i see more skel stuff inside the tree and i think that it needs
> > > some discussion or at least don't use skeleton as part of a file name
> > > that will be compiled. AFAIK, we've some of them sitting at
> > > arch/m68k/..., but i can't check atm. What do you think?
> > >
> >
> >
> > Why not make a Documentation/driver-skeletons.txt? I can write it, if everyone
> > can point me in the direction of where all the skeleton and example files are.
>
> I agree, you're free to submit it but i've no idea if it will be
> accepted.
as greg already said, you won't expect code under Documentation.
i won't push such patches.
please pick something usefull.
--
maks
kernel janitor http://janitor.kernelnewbies.org/
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2004-12-10 10:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 15:54 [KJ] patches: delete 75 unused files Domen Puncer
2004-12-08 16:08 ` Greg KH
2004-12-08 16:55 ` Adrian Bunk
2004-12-08 17:05 ` Gustavo Franco
2004-12-08 17:13 ` Greg KH
2004-12-08 17:24 ` Gustavo Franco
2004-12-08 22:15 ` Jim Nelson
2004-12-09 12:52 ` Gustavo Franco
2004-12-10 10:43 ` maximilian attems [this message]
2004-12-10 10:44 ` maximilian attems
2004-12-10 10:51 ` maximilian attems
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041210104308.GC2211@stro.at \
--to=janitor@sternwelten.at \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.