From: Joe Perches <joe@perches.com>
To: "Peter Hüwe" <PeterHuewe@gmx.de>
Cc: David Vrabel <david.vrabel@csr.com>,
Jiri Kosina <trivial@kernel.org>,
kernel-janitors@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Fix entry for uwb to include subdirectories
Date: Tue, 22 Dec 2009 02:59:11 -0800 [thread overview]
Message-ID: <1261479551.1895.43.camel@Joe-Laptop.home> (raw)
In-Reply-To: <200912221130.30586.PeterHuewe@gmx.de>
On Tue, 2009-12-22 at 11:30 +0100, Peter Hüwe wrote:
> Okay I guess it IS correct
Maybe it is.
David Vrabel should be able to ack/nack it.
By default, get_maintainer checks a 1 year history
for commits. If a file hasn't had a modification
in over a year, it likely isn't maintained, it's
already perfect or it's obsolete.
You could change the get_maintainer history window
with --git-since=date
Anyway, if get_maintainer doesn't give you a result,
look at the git log for the file or look inside the
source code of the file itself.
Here's the _only_ commit for that file:
$ git log drivers/uwb/i1480/i1480-est.c
commit 1ba47da527121ff704f4e9f27a12c9f32db05022
Author: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
Date: Wed Sep 17 16:34:20 2008 +0100
uwb: add the i1480 DFU driver
Add the driver for downloading the firmware to an Intel i1480 device.
Signed-off-by: David Vrabel <david.vrabel@csr.com>
And in the file:
* Copyright (C) 2005-2006 Intel Corporation
* Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
So you should add Inaky to your patch cc list.
cheers, Joe
next prev parent reply other threads:[~2009-12-22 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 9:05 Peter Huewe
2009-12-22 9:22 ` Joe Perches
2009-12-22 10:23 ` Peter Hüwe
2009-12-22 10:30 ` Peter Hüwe
2009-12-22 10:59 ` Joe Perches [this message]
2009-12-22 12:26 ` David Vrabel
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=1261479551.1895.43.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=PeterHuewe@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=david.vrabel@csr.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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
all inboxes | Powered by JetHome®