From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Joe Perches <joe@perches.com>, Paul Mundt <lethal@linux-sh.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 08/10] MAINTAINERS - Add FTRACE git
Date: Wed, 14 Jan 2009 23:37:53 +0100 [thread overview]
Message-ID: <20090114223753.GB19173@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0901140811530.6759@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> > maybe:
> >
> > T: git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-tip.git auto-ftrace-next
> >
> > No idea what's right here. I had some private emails
> > with Steven Rostedt about a git tree. He suggested
> > to use tip.
> >
> > Steven? Suggestions?
>
> Ingo usually pulls ftrace related patches into the tracing/ftrace
> branch. That is for core ftrace. Since ftrace has a bunch of pluggins,
> they may have their own branches.
for a stable Git reference for tracing development i'd suggest
tip/tracing/core.
The 'core' topic branch is where the known-stable tracing topics are
merged into. The other topic branches can include known-broken or
known-WIP bits.
Ingo
next prev parent reply other threads:[~2009-01-14 22:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 20:28 [PATCH 0/10] MAINTAINERS - script, patterns, and misc fixes Joe Perches
2009-01-13 20:28 ` [PATCH 01/10] Add scripts/get_maintainer.pl Joe Perches
2009-01-13 20:28 ` [PATCH 02/10] MAINTAINERS - Add file patterns Joe Perches
2009-01-13 20:28 ` [PATCH 03/10] MAINTAINERS - Standardize style Joe Perches
2009-01-13 20:28 ` [PATCH 04/10] MAINTAINERS - Remove CS4280 Joe Perches
2009-01-13 20:28 ` [PATCH 05/10] MAINTAINERS - Remove HP Fibre Channel HBA no longer in tree Joe Perches
2009-01-13 20:28 ` [PATCH 06/10] MAINTAINERS - standardize "T: git urls" Joe Perches
2009-01-13 20:28 ` [PATCH 07/10] MAINTAINERS - Add Linus Torvalds' git Joe Perches
2009-01-13 20:28 ` [PATCH 08/10] MAINTAINERS - Add FTRACE git Joe Perches
2009-01-14 5:59 ` Paul Mundt
2009-01-14 6:19 ` Joe Perches
2009-01-14 13:16 ` Steven Rostedt
2009-01-14 13:35 ` Frédéric Weisbecker
2009-01-14 22:37 ` Ingo Molnar [this message]
2009-01-13 20:28 ` [PATCH 09/10] MAINTAINERS - i2c_tiny_usb T: should be W: Joe Perches
2009-01-13 20:28 ` [PATCH 10/10] MAINTAINERS - Update FPU Emulator contact address and web page Joe Perches
2009-01-13 20:54 ` [PATCH 0/10] MAINTAINERS - script, patterns, and misc fixes Andrew Morton
2009-01-14 3:49 ` Joe Perches
2009-01-14 4:26 ` Joe Perches
2009-01-14 7:13 ` Andrew Morton
2009-01-14 7:21 ` Joe Perches
2009-01-14 19:37 ` Joe Perches
2009-01-14 19:55 ` Joe Perches
2009-01-14 9:30 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2008-11-18 17:13 [PATCH 0/10] MAINTAINERS - add script and patterns Joe Perches
2008-11-18 17:13 ` [PATCH 08/10] MAINTAINERS - Add FTRACE git Joe Perches
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=20090114223753.GB19173@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rostedt@goodmis.org \
--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
all inboxes | Powered by JetHome®