From: Sam Ravnborg <sam@ravnborg.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Martin Bligh <mbligh@google.com>,
Christoph Hellwig <hch@infradead.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Al Viro <viro@zeniv.linux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Stephane Eranian <eranian@googlemail.com>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] Performance Counters for Linux
Date: Thu, 11 Jun 2009 23:26:35 +0200 [thread overview]
Message-ID: <20090611212635.GA9446@uranus.ravnborg.org> (raw)
In-Reply-To: <1244755036.27363.93.camel@violet>
On Thu, Jun 11, 2009 at 11:17:16PM +0200, Marcel Holtmann wrote:
> Hi Sam,
>
> > > So you are saying that only good code comes from including it into
> > > linux-2.6.git and otherwise you will never get there. Have you actually
> > > tried to maintain this in a separate repository on kernel.org?
> >
> > Could you please remind us what the arguments agains including a few
> > seleted tools within the kernel source tree was.
> >
> > I ask because I really cannot see why so much nosie is generated?
> > As a naive user that like easy access to the stuff I work with
> > this looks like an optimal place to find the kernel-hacking
> > tools I need. Why should I hunt somewhere else to find it?
>
> I personally would expect a perf.git on kernel.org for the userspace
> tools for it. Like we have udev.git there, iproute2.git and others.
>
> Seems to be working perfectly fine (except of course oprofile) and makes
> packaging and security updates a lot easier.
There is nothing preventing us from adding support for rpm and source rpms.
So you just grab the relevant tre and issue a few cammnds and you have your
packages.
And for security fixes we have the stable kernels.
> The distros have always a
> really hard problem with releasing new kernel packages.
There is nothing that say that because the code live inside
the kernel tree you _have_to_ release the full kernel source
to release a tool.
You mix up the fact that the source for the tool live inside the
kernel with the way tools are packaged.
Sam
next prev parent reply other threads:[~2009-06-11 21:24 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 16:03 [GIT PULL] Performance Counters for Linux Ingo Molnar
2009-06-11 16:17 ` Christoph Hellwig
2009-06-11 16:26 ` Linus Torvalds
2009-06-11 16:34 ` Marcel Holtmann
2009-06-11 16:38 ` Linus Torvalds
2009-06-11 16:46 ` Christoph Hellwig
2009-06-11 16:54 ` Linus Torvalds
2009-06-11 16:47 ` Marcel Holtmann
2009-06-11 18:04 ` David Newall
2009-06-11 16:52 ` Al Viro
2009-06-11 16:56 ` Peter Zijlstra
2009-06-11 17:00 ` Christoph Hellwig
2009-06-11 17:05 ` Ray Lee
2009-06-11 17:08 ` Marcel Holtmann
2009-06-11 17:12 ` Al Viro
2009-06-11 17:22 ` Ray Lee
2009-06-11 17:06 ` Linus Torvalds
2009-06-11 17:59 ` Pekka Enberg
2009-06-11 18:10 ` David Newall
2009-06-11 18:21 ` Linus Torvalds
2009-06-11 18:38 ` David Newall
2009-06-11 18:44 ` Linus Torvalds
2009-06-11 19:07 ` David Newall
2009-06-11 19:23 ` Linus Torvalds
2009-06-11 19:29 ` Linus Torvalds
2009-06-11 19:35 ` David Newall
2009-06-11 19:49 ` Linus Torvalds
2009-06-12 1:43 ` Robert Richter
2009-06-12 3:21 ` David Newall
2009-06-11 19:37 ` David Newall
2009-06-11 18:51 ` Christoph Hellwig
2009-06-11 19:05 ` Marcel Holtmann
2009-06-11 18:24 ` Martin Bligh
2009-06-11 18:34 ` Linus Torvalds
2009-06-11 20:23 ` Ingo Molnar
2009-06-11 20:49 ` Marcel Holtmann
2009-06-11 21:08 ` Sam Ravnborg
2009-06-11 21:17 ` Marcel Holtmann
2009-06-11 21:26 ` Sam Ravnborg [this message]
2009-06-11 22:18 ` Jiri Slaby
2009-06-11 22:27 ` Linus Torvalds
2009-06-11 22:38 ` Alan Cox
2009-06-11 22:49 ` Linus Torvalds
2009-06-12 7:35 ` Alan Cox
2009-06-11 23:19 ` Al Viro
2009-06-11 23:25 ` Linus Torvalds
2009-06-12 0:26 ` Al Viro
2009-06-12 2:58 ` Linus Torvalds
2009-06-12 4:05 ` Al Viro
2009-06-11 21:59 ` Steven Rostedt
2009-06-12 10:19 ` Jörn Engel
2009-06-11 21:14 ` Ingo Molnar
2009-06-28 1:19 ` Felipe Contreras
2009-06-11 19:58 ` Andrew Morton
2009-06-11 20:09 ` Linus Torvalds
2009-06-12 4:07 ` Kyle McMartin
2009-06-11 16:58 ` Linus Torvalds
2009-06-11 18:50 ` Sam Ravnborg
2009-06-15 13:41 ` Giacomo A. Catenazzi
2009-06-15 15:18 ` Sam Ravnborg
2009-06-12 9:56 ` stephane eranian
2009-06-12 10:28 ` Ingo Molnar
2009-06-18 21:58 ` stephane eranian
2009-06-22 13:10 ` Performance analysis under Linux (was: Re: [GIT PULL] Performance Counters for Linux) 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=20090611212635.GA9446@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eranian@googlemail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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