public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: matt mooney <mfm@muteddisk.com>
Cc: Greg Ungerer <gerg@snapgear.com>, Greg Ungerer <gerg@uclinux.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Howells <dhowells@redhat.com>,
	Tim Abbott <tabbott@ksplice.com>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 08/20] m68knommu: change to new flag variables
Date: Wed, 29 Sep 2010 16:36:59 +0200	[thread overview]
Message-ID: <4CA34F0B.6010605@suse.cz> (raw)
In-Reply-To: <20100928071606.GA13303@haskell.muteddisk.com>

On 28.9.2010 09:16, matt mooney wrote:
> My original intent was through the maintainer trees; however, I am starting to
> realize that it probably would have been best to all go into the kbuild tree as
> one patch series. That being said, some people have picked them up and others
> have just acked, so really whatever is easiest for you. All unapplied will
> eventually go through the kbuild tree.

Please try push as much through maintainer trees as possible, to avoid
unnecessary merge conflicts. Of course, if you end up with some patches
that nobody is picking up, I'll apply them to the kbuild tree.

Thanks,
Michal

  parent reply	other threads:[~2010-09-29 14:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23  6:50 [PATCH 08/20] m68knommu: change to new flag variables matt mooney
2010-09-28  6:41 ` Greg Ungerer
2010-09-28  7:16   ` matt mooney
2010-09-28 13:22     ` Greg Ungerer
2010-09-29 14:36     ` Michal Marek [this message]
2010-09-29 23:15       ` matt mooney
2010-09-30 20:51         ` Michal Marek

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=4CA34F0B.6010605@suse.cz \
    --to=mmarek@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfm@muteddisk.com \
    --cc=tabbott@ksplice.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