public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: John Kacur <jkacur@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	rostedt@goodmis.org, linux-kernel@vger.kernel.org,
	mathieu.desnoyers@polymtl.ca, a.p.zijlstra@chello.nl,
	fweisbec@gmail.com, acme@redhat.com, mhiramat@redhat.com,
	postmaster@vger.kernel.org
Subject: Re: mailing list for trace users
Date: Wed, 23 Sep 2009 21:49:57 +0200	[thread overview]
Message-ID: <20090923194957.GA19358@elte.hu> (raw)
In-Reply-To: <520f0cf10909231240g11f5cafei5cbb4ed494eba76d@mail.gmail.com>


* John Kacur <jkacur@gmail.com> wrote:

> On Wed, Sep 23, 2009 at 9:30 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * David Miller <davem@davemloft.net> wrote:
> >
> >> From: Ingo Molnar <mingo@elte.hu>
> >> Date: Wed, 23 Sep 2009 13:47:25 +0200
> >>
> >> > Could you please also create the linux-perf-users list, for perf
> >> > events and the perf tool related user questions? (We have asked for
> >> > this before but must have gotten lost somewhere)
> >>
> >> I think your communities are similar enough and small enough that you
> >> could share this list.
> >
> > It's two separate subsystems. There's a lot of non-tracing aspects of
> > performance events: it does profiling, counting, latency analysis, etc.
> > The tool is named 'perf', the subsystem is named 'performance events',
> > and the most typical workflows dont do any tracing.
> >
> > And i beg to differ about the size of the communities. It's just been
> > added upstream...
> >
> > Also, what is the policy for adding new lists to vger.kernel.org? If a
> > subsystem maintainer asks for a list named after a core kernel
> > subsystem, how frequently is it rejected, and on what basis?
> >
> > I find it sad that such an arbitrary looking negative decision from you
> > forces a user list away from vger. I wouldnt mind it to be closed if it
> > has no significant traffic after a year or lifetime or so - many vger
> > lists have almost no traffic to begin with.
> >
> > Also, i cannot help but to observe the fact that you've fought the 
> > original perfcounters project in a very ugly and public way less 
> > than a year ago. Dont you think that you 'deciding' this matter in 
> > such a negative fashion is a conflict of interest?
> >
> > ? ? ? ?Ingo
> 
> Yikes - Ingo, I don't want to spawn a long thread here about what to 
> call the list, but as a native English speaker, I think that 
> "linux-trace-users" sounds much nicer than "linux-tracing-users".

That argument i can and will accept of course ...

The "sorry, i ignored you twice and now it's unfortunately too late" 
excuse given by David i will not ;-)

Note that this mail you replied to was about 
linux-perf-users@vger.kernel.org, which David refused to create, 
suggesting that perf users should mail to 
linux-trace-users@vger.kernel.org instead. (which is a curious argument 
- if you use a tool named 'perf', or if you are using PAPI to count 
events, would it occur to you to mail to that list?)

	Ingo

  parent reply	other threads:[~2009-09-23 19:50 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 20:16 mailing list for trace users Steven Rostedt
2009-09-21 19:17 ` Frederic Weisbecker
2009-09-22  0:46   ` Li Zefan
2009-09-22  9:31     ` Ingo Molnar
2009-09-21 19:50 ` John Kacur
2009-09-22  9:13 ` Avi Kivity
2009-09-22 10:59   ` Peter Zijlstra
2009-09-22 11:51     ` Mike Galbraith
2009-09-22 11:18   ` Mike Galbraith
2009-09-22 11:28   ` Mike Galbraith
2009-09-22 11:34     ` Avi Kivity
2009-09-22 11:47       ` Mike Galbraith
2009-09-22 11:51         ` Avi Kivity
2009-09-22 11:54           ` Mike Galbraith
2009-09-22 13:53             ` Mike Galbraith
2009-09-22 14:03               ` Avi Kivity
2009-09-22 19:09                 ` Mike Galbraith
2009-09-22 19:14                   ` Avi Kivity
2009-09-23  8:26                     ` Mike Galbraith
2009-09-22 20:17           ` [perf] Finding uninstalled modules Was " Arnaldo Carvalho de Melo
2009-09-23  8:31             ` Avi Kivity
2009-09-23  8:37               ` Arnaldo Carvalho de Melo
2009-09-23  9:15               ` Ingo Molnar
2009-09-23  9:20               ` [patch] " Mike Galbraith
2009-09-23  9:55                 ` Avi Kivity
2009-09-23 10:02                   ` Mike Galbraith
2009-09-23 11:31                   ` Mike Galbraith
2009-09-23 12:00                     ` Mike Galbraith
2009-09-23 12:58                     ` Avi Kivity
2009-09-23 13:06                       ` Mike Galbraith
2009-09-23 13:10                       ` Avi Kivity
2009-09-23 13:50                         ` Mike Galbraith
2009-09-23 14:00                           ` Avi Kivity
2009-09-23 14:09                             ` Mike Galbraith
2009-09-23 14:39                               ` Avi Kivity
2009-09-23 14:52                                 ` Mike Galbraith
2009-09-23 14:56                                   ` Avi Kivity
2009-09-23 15:05                                     ` Mike Galbraith
2009-09-23 15:09                                       ` Avi Kivity
2009-09-23 15:26                                         ` Mike Galbraith
2009-09-24  8:07                                         ` Mike Galbraith
2009-09-24 11:01                                           ` [tip:perf/urgent] perf tools: Handle relative paths while loading module symbols tip-bot for Mike Galbraith
2009-09-23 11:49                 ` [tip:perf/urgent] perf tools: Fix module symbol loading bug tip-bot for Mike Galbraith
2009-09-22 22:32 ` mailing list for trace users David Miller
2009-09-23 11:47   ` Ingo Molnar
2009-09-23 16:45     ` Masami Hiramatsu
2009-09-23 17:00       ` Ingo Molnar
2009-09-23 18:07         ` Masami Hiramatsu
2009-09-23 20:07           ` Ingo Molnar
2009-09-23 18:14     ` David Miller
2009-09-23 19:30       ` Ingo Molnar
2009-09-23 19:40         ` John Kacur
2009-09-23 19:42           ` John Kacur
2009-09-23 19:59             ` Ingo Molnar
2009-09-23 21:24               ` Steven Rostedt
2009-09-23 21:41                 ` Ingo Molnar
2009-09-23 21:56                 ` Ingo Molnar
2009-09-23 19:49           ` Ingo Molnar [this message]
2009-09-23 20:08             ` John Kacur
2009-09-23 21:54         ` David Miller
2009-09-23 22:02           ` Ingo Molnar
2009-09-23 22:47         ` David Miller
2009-09-24 11:51           ` Ingo Molnar
2009-09-23 11:48   ` Ingo Molnar
2009-09-23 18:12     ` David Miller
2009-09-23 19:41       ` Ingo Molnar
2009-09-23 21:55         ` David Miller
2009-09-23 22:10           ` Ingo Molnar
2009-09-23 22:41             ` David Miller
2009-09-24 11:16               ` Ingo Molnar
2009-09-24 16:40                 ` David Miller
2009-09-24 18:58                 ` David Miller
2009-09-24 19:22                   ` Ingo Molnar

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=20090923194957.GA19358@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jkacur@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mhiramat@redhat.com \
    --cc=postmaster@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox