Kumba wrote:
Here's where we want the non-devs to get access. After all, not all
development and debugging is done by devs. All the current devs were,
at one point, users. Where did they get their start? My bet is they
entered via the -dev mailing list, learned the ropes here, and
event
Kumba wrote:
- I envisioned three mailing lists, essentially:
* core
* dev
* project
- core:private, dev-only mailing list for internal discussion
* Possibility: becomes read-only to the public after
a set time limit, possibly 1, 2,
Robin H. Johnson wrote:
> Software, I picked up maintenance of autofs when the previous maintainer went
> AWOL several years ago, and ran with it because I needed AutoFS-LDAP. I don't
> have access to any AutoFS-LDAP setups anymore, and upstream has moved on.
> There
> is a 7Kb init.d script that
Greg KH wrote:
> On Tue, Jul 10, 2007 at 07:10:35PM +0200, Dominique Michel wrote:
Can you explain more. If the kernel can be tivoized by someone
>>> I'm sorry, but "tivoized" is not a verb. Please explain what you mean
>>> by this.
>> I mean if someone distribute a kernel with a licence that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Mauch wrote:
>
> 5) considering 3), I'd rather see such information be specified by
> ebuilds somehow, not a global file (think about overlays). Maybe by
> installing a script in a specific location or so.
>
> Marius
How about adding another fun
