From: Paul Mundt <lethal@linux-sh.org>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: "Wu, Bryan" <bryan.wu@analog.com>, Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] Blackfin arch: add kdebug header file
Date: Tue, 27 Mar 2007 13:49:14 +0900 [thread overview]
Message-ID: <20070327044914.GA26099@linux-sh.org> (raw)
In-Reply-To: <8bd0f97a0703262134h20bdf8dcqb1043ca176a7149c@mail.gmail.com>
On Tue, Mar 27, 2007 at 12:34:25AM -0400, Mike Frysinger wrote:
> On 3/26/07, Paul Mundt <lethal@linux-sh.org> wrote:
> >You should really consider the latter for getting updates merged in the
> >future
>
> we're planning for this, but the short term it isnt doable for us
>
If you think mangling patches by hand is a more effective use of time, no
one is stopping you -- some people even prefer that. On the other hand, if
you're struggling with an effective methodology before things are merged,
what reason is there to suspect that things will get better afterwards?
Going by Bryan's post, it's clear that the current system isn't working
for you at least.
next prev parent reply other threads:[~2007-03-27 4:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 10:12 [PATCH -mm] Blackfin arch: add kdebug header file Wu, Bryan
2007-03-26 21:45 ` Arnd Bergmann
2007-03-27 3:40 ` Wu, Bryan
2007-03-27 3:57 ` Paul Mundt
2007-03-27 4:34 ` Mike Frysinger
2007-03-27 4:49 ` Paul Mundt [this message]
2007-03-27 5:17 ` Mike Frysinger
2007-03-27 5:27 ` Randy Dunlap
2007-03-27 5:40 ` Wu, Bryan
2007-03-27 8:27 ` Sam Ravnborg
2007-03-27 15:34 ` Randy Dunlap
2007-03-28 2:06 ` Wu, Bryan
2007-03-28 2:13 ` Randy Dunlap
2007-03-27 5:32 ` Wu, Bryan
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=20070327044914.GA26099@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bryan.wu@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@gmail.com \
/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