lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 22 Sep 2009 11:31:55 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Li Zefan <lizf@...fujitsu.com>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	postmaster@...r.kernel.org
Subject: Re: mailing list for trace users


* Li Zefan <lizf@...fujitsu.com> wrote:

> Frederic Weisbecker wrote:
> > On Wed, Sep 16, 2009 at 04:16:22PM -0400, Steven Rostedt wrote:
> >> What are people's thoughts about creating a linux-trace-users mailing
> >> list on vger.kernel.org?
> >>
> >> This would be a place for users of tracers and even perf. For asking
> >> questions about how to use the debugfs/tracing directory or the perf
> >> tool.
> >>
> >> This will not be a place for kernel development. Patches for the tracing
> >> infrastructure should still go through LKML. This will be a place to ask
> >> how-to questions, or any other kind of help questions.
> >>
> >> LKML can be quite intimidating, and it is not a place to ask help
> >> questions anyway. I think adding a linux-trace-users mailing list would
> >> be a good idea.
> >>
> >> Thoughts?
> >>
> >> -- Steve
> > 
> > 
> > Why not. That could also gather informations from LKML threads by 
> > Cc'ing it while explaining how to use the tools in random 
> > discussions.
> > 
> 
> +1
> 
> And then the mailing list needs to be renamed to linux-trace. And we 
> need to advertise it, in Documentation, Kconfig?

The list i can support is what was suggested here: 
tracing-users@...r.kernel.org, for user questions and solutions.

Development of tracing bits should still be very much done on lkml.

We dont want to go down the failed path of some other projects that went 
off to their private lists, became self-breeding, ego-boosting 
pat-each-other-on-the-shoulders-for-being-cool-guys forums, became more 
and more detached from mainline and the complexities there, and in some 
cases also became increasingly hostile towards mainline (hey everyone on 
that list agrees that we are cool guys writing cool code, why doesnt 
upstream love us unconditionally?) and sometimes started growing clique 
or clan social structures - which are outright harmful.

The topical filtering offered by such lists is an advantage (note that 
those can be had on lkml as well by using mail filtering) - but the 
social disadvantages are unsolvable, lets not go there.

Staying on lkml and staying connected is particularly important for a 
subsystem that by their very nature deal with many other subsystems, 
such as tracing / instrumentation.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ