>
> On Tue, 13 Jan 2009, Joe Perches wrote:
>
>> On Wed, 2009-01-14 at 14:59 +0900, Paul Mundt wrote:
>> > On Tue, Jan 13, 2009 at 12:28:16PM -0800, Joe Perches wrote:
>> > > Signed-off-by: Joe Perches <joe@perches.com>
>> > > ---
>> > > MAINTAINERS | 1 +
>> > > 1 files changed, 1 insertions(+), 0 deletions(-)
>> > >
>> > > diff --git a/MAINTAINERS b/MAINTAINERS
>> > > index ceeeb8c..6e051c3 100644
>> > > --- a/MAINTAINERS
>> > > +++ b/MAINTAINERS
>> > > @@ -2189,6 +2189,7 @@ F: fs/freevxfs/
>> > > FTRACE
>> > > P: Steven Rostedt
>> > > M:
rostedt@goodmis.org
>> > > +T: git git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-tip.git
>> > > S: Maintained
>> > > F: Documentation/ftrace.txt
>> > > F: arch/*/*/*/ftrace.h
>> >
>> > This sort of thing only makes sense if you include the topic branch for
>> > the tree in question. While it is true that ftrace development happens in
>> > this tree, people looking at ftrace may not want to sort through the
>> > hundreds of unrelated topic branches in the process. I say this as
>> > someone that does not want to sort through hundreds of unrelated topic
>> > branches in search of ftrace code ;-)
>>
>>
http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=heads
>>
>> Is the correct topic branch for ftrace auto-ftrace-next?
>
> That is just a location that Ingo places changes that are ready to go to
> linux-next. Not where development is.
>
>>
>> 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.
>
> But to answer Paul's question, I would suggest tracing/ftrace for
> seeing latest core ftrace changes.
