public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Paul Mundt <lethal@linux-sh.org>, Steven Rostedt <rostedt@goodmis.org>
Cc: 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: Tue, 13 Jan 2009 22:19:47 -0800	[thread overview]
Message-ID: <1231913987.30095.11.camel@localhost> (raw)
In-Reply-To: <20090114055954.GA7039@linux-sh.org>

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?

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?


  reply	other threads:[~2009-01-14  6:20 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 [this message]
2009-01-14 13:16       ` Steven Rostedt
2009-01-14 13:35         ` Frédéric Weisbecker
2009-01-14 22:37         ` Ingo Molnar
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=1231913987.30095.11.camel@localhost \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --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