From: Pete Zaitcev <zaitcev@redhat.com>
To: joe@perches.com
Cc: torvalds@linux-foundation.org,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] [490/2many] MAINTAINERS - USB BLOCK DRIVER (UB ub)
Date: Mon, 13 Aug 2007 00:04:40 -0700 [thread overview]
Message-ID: <20070813000440.fedfa634.zaitcev@redhat.com> (raw)
In-Reply-To: <46bffc48.jq7Ax2MlK/hZ/ANM%joe@perches.com>
I received two updates, and something jumped out:
On Sun, 12 Aug 2007 23:38:00 -0700, joe@perches.com wrote:
> +F: drivers/block/ub.c
On Sun, 12 Aug 2007 23:38:30 -0700, joe@perches.com wrote:
> +F: /drivers/usb/class/usblp.c
Why do some patterns start with a leading slash and others do not?
-- Pete
next prev parent reply other threads:[~2007-08-13 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:38 [PATCH] [490/2many] MAINTAINERS - USB BLOCK DRIVER (UB ub) joe
2007-08-13 7:04 ` Pete Zaitcev [this message]
2007-08-13 7:11 ` Joe Perches
2007-08-13 14:11 ` Stefan Richter
2007-08-13 15:55 ` Joe Perches
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=20070813000440.fedfa634.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=torvalds@linux-foundation.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