From: Li Zefan <lizefan@huawei.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Joe Perches <joe@perches.com>, <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: MAINTAINERS: missing git trees
Date: Fri, 15 Jun 2012 11:40:37 +0800 [thread overview]
Message-ID: <4FDAAEB5.5050002@huawei.com> (raw)
In-Reply-To: <20120615025751.GB8250@localhost>
On 2012/6/15 10:57, Fengguang Wu wrote:
> Hi Joe,
>
> On Thu, Jun 14, 2012 at 07:34:21PM -0700, Joe Perches wrote:
>> These git trees listed in MAINTAINERS don't seem to exist.
>
> Yeah I noticed this, too, several days ago.
>
>> Should they be deleted?
>
> Some trees are no longer exist (ie. netfilter), some are moved. For
> example, the btrfs tree is
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
>
There's already a patch sent to btrfs mailing list to update this.
> Perhaps it works best to notify the corresponding email addresses and
> ask for update patches. Then after some time, delete the remaining
> dead trees.
prev parent reply other threads:[~2012-06-15 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 2:34 Joe Perches
2012-06-15 2:57 ` Fengguang Wu
2012-06-15 3:07 ` Joe Perches
2012-06-15 3:32 ` Fengguang Wu
2012-06-15 3:40 ` Li Zefan [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=4FDAAEB5.5050002@huawei.com \
--to=lizefan@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome