[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090114223753.GB19173@elte.hu>
Date: Wed, 14 Jan 2009 23:37:53 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Joe Perches <joe@...ches.com>, Paul Mundt <lethal@...ux-sh.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Pavel Machek <pavel@....cz>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 08/10] MAINTAINERS - Add FTRACE git
* Steven Rostedt <rostedt@...dmis.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
--
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