All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/3] ftrace: start stop infrastructure changes
Date: Thu, 6 Nov 2008 07:52:40 +0100	[thread overview]
Message-ID: <20081106065240.GC15731@elte.hu> (raw)
In-Reply-To: <20081105212428.148612398@goodmis.org>


* Steven Rostedt <rostedt@goodmis.org> wrote:

>  Note, I'm now trying to learn to use git. I am experimenting with
>  using a combination of quilt and git. I set up a git repo at:
> 
>  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> 
>  This series is in the tip/devel branch.
> 
>  I'll put my changes in that branch and then send out the patches
>  as I have always done. But the introduction will list the shortlog
>  of the changes, then followed by the patches themselves.
> 
>  I do this by using git format-patch and then having quilt send
>  out the queue that was produced.
> 
>  I plan on automating a lot of this, but for this run, it was
>  done manually.

Worked fine on my side - and it's easier than processing patches in 
email: the ordering and dependencies are more obvious.

The only flip side is that it's harder to fix small details in commit 
logs in an ad-hoc way. So be prepared to see more nitpicking from me 
for such details :-)

	Ingo

      parent reply	other threads:[~2008-11-06  6:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 21:24 [PATCH 0/3] ftrace: start stop infrastructure changes Steven Rostedt
2008-11-05 21:24 ` [PATCH 1/3] ftrace: add quick function trace stop Steven Rostedt
2008-11-05 21:24 ` [PATCH 2/3] ftrace: soft tracing stop and start Steven Rostedt
2008-11-05 21:24 ` [PATCH 3/3] ftrace: restructure tracing start/stop infrastructure Steven Rostedt
2008-11-06  6:52 ` Ingo Molnar [this message]

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=20081106065240.GC15731@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.