Synopsis: i am tired computer wackers are being able mess with our stuff. have
we not much more of a smartness than that. this even have to be written . this
ignorance. we are not an ignorant county
State-Changed-From-To: open-closed
State-Changed-By: linimon
State-Changed-When: Tue May
Synopsis: thsrokzb
State-Changed-From-To: open-closed
State-Changed-By: linimon
State-Changed-When: Sat Feb 13 19:15:36 UTC 2010
State-Changed-Why:
spam attack
http://www.freebsd.org/cgi/query-pr.cgi?pr=143903
___
freebsd-advocacy@freebsd.org mailing
Synopsis: enzrtyin
State-Changed-From-To: open-closed
State-Changed-By: linimon
State-Changed-When: Wed May 26 14:21:23 UTC 2010
State-Changed-Why:
spam run.
http://www.freebsd.org/cgi/query-pr.cgi?pr=147070
___
freebsd-advocacy@freebsd.org mailing
On Sun, Mar 04, 2018 at 11:24:34PM -0500, Andras Farkas wrote:
> What do you have to hide from FreeBSD users? Why should users trust
> people who hide things from them?
When I posted email to an internal list, I was under the impression
that it would remain confidential.
Someone, I don't know
On Mon, Mar 05, 2018 at 02:48:26PM -0500, Stephen Cook wrote:
> The problem with the Foundation sponsoring a CoC is that a small group
> of extremists forced their way in to generate and implement their own
> set of rules, secretly.
This is exactly not what happened.
> I suspect from the lack of
On Mon, Mar 05, 2018 at 05:17:59PM -0500, Stephen Cook wrote:
> On 2018-03-05 15:51, Mark Linimon wrote:
> > On Mon, Mar 05, 2018 at 02:48:26PM -0500, Stephen Cook wrote:
> >> The problem with the Foundation sponsoring a CoC is that a small group
> >> of extremists forc
On Mon, Mar 05, 2018 at 11:46:59PM +0100, Julian H. Stacey wrote:
> I agree with the other person's thoughts that FreeBSD fixes uncommited
> for years destroys incentive to file more fixes.
I do not know anyone who disagrees with this.
The issue is how to get people involved with this utterly
