All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	David Woodhouse <dwmw2@infradead.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-mtd <linux-mtd@lists.infradead.org>
Subject: l2-mtd-2.6.git to linux-next
Date: Mon, 06 Jun 2011 10:37:30 +0300	[thread overview]
Message-ID: <1307345850.3135.24.camel@localhost> (raw)

Stephen,

as we've discussed, please, include l2-mtd-2.6.git tree to linux-next:

git://git.infradead.org/users/dedekind/l2-mtd-2.6.git master

David, Stephen would like to see your explicit ack.

To make a long story short, currently the MTD subsystem maintenance is a
team work:

1. David is the maintainer who has the ultimate authority to merge or
   reject patches, and who holds the biggest MTD experience/knowledge.

2. David is busy with other projects and has no time to routinely
   review patches and merge them to the mtd-2.6.git tree. And I help him
   with my "level 2" l2-mtd-2.6.git tree.

By including l2-mtd-2.6.git into linux-next we want to solve the
following problem: because of lack of time dwmw2 does not always merges
patches to the mtd-2.6.git tree, and often we are in a situation when
MTD patches are exposed to linux-next for a day or 2, during the merge
window, and then they are merged.

Thanks!

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	David Woodhouse <dwmw2@infradead.org>
Cc: linux-next@vger.kernel.org,
	linux-mtd <linux-mtd@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: l2-mtd-2.6.git to linux-next
Date: Mon, 06 Jun 2011 10:37:30 +0300	[thread overview]
Message-ID: <1307345850.3135.24.camel@localhost> (raw)

Stephen,

as we've discussed, please, include l2-mtd-2.6.git tree to linux-next:

git://git.infradead.org/users/dedekind/l2-mtd-2.6.git master

David, Stephen would like to see your explicit ack.

To make a long story short, currently the MTD subsystem maintenance is a
team work:

1. David is the maintainer who has the ultimate authority to merge or
   reject patches, and who holds the biggest MTD experience/knowledge.

2. David is busy with other projects and has no time to routinely
   review patches and merge them to the mtd-2.6.git tree. And I help him
   with my "level 2" l2-mtd-2.6.git tree.

By including l2-mtd-2.6.git into linux-next we want to solve the
following problem: because of lack of time dwmw2 does not always merges
patches to the mtd-2.6.git tree, and often we are in a situation when
MTD patches are exposed to linux-next for a day or 2, during the merge
window, and then they are merged.

Thanks!

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

             reply	other threads:[~2011-06-06  7:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06  7:37 Artem Bityutskiy [this message]
2011-06-06  7:37 ` l2-mtd-2.6.git to linux-next Artem Bityutskiy
2011-06-07  4:40 ` Artem Bityutskiy
2011-06-07  4:40   ` Artem Bityutskiy
2011-06-07 10:55   ` David Woodhouse
2011-06-07 10:55     ` David Woodhouse
2011-06-08  0:31 ` Stephen Rothwell
2011-06-08  0:31   ` Stephen Rothwell

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=1307345850.3135.24.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.