From: Paul LeoNerd Evans <leonerd@leonerd.org.uk>
To: bluez-users@lists.sourceforge.net
Cc: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] what does the 'mh10' stand for as in patch-2.4.21-mh10 ?
Date: Fri, 8 Dec 2006 09:03:09 +0000 [thread overview]
Message-ID: <20061208090309.70aa7bef@nim.leo> (raw)
In-Reply-To: <20061207065924.GA12888@163.com>
[-- Attachment #1.1: Type: text/plain, Size: 619 bytes --]
On Thu, 7 Dec 2006 14:59:24 +0800
amateur <ztl.post@gmail.com> wrote:
> I have seen some kernel patch for bluetooth subsystem on the bluez
> homepage, which are named as patch-2.4.21-mh10.gz or so. What does the
> mh10 mean?
As is usual with personal patches on the kernel, it stands for the
initials of the maintainer; am[n] for Andrew Morten's tree, for example.
These ones stand for Marcel Holtmann. The 10 means it's the 10th version
of a patch for this kernel (2.4.21).
--
Paul "LeoNerd" Evans
leonerd@leonerd.org.uk
ICQ# 4135350 | Registered Linux# 179460
http://www.leonerd.org.uk/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-12-08 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 6:59 [Bluez-users] what does the 'mh10' stand for as in patch-2.4.21-mh10 ? amateur
2006-12-08 9:03 ` Paul LeoNerd Evans [this message]
2006-12-09 1:40 ` amateur
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=20061208090309.70aa7bef@nim.leo \
--to=leonerd@leonerd.org.uk \
--cc=bluez-users@lists.sourceforge.net \
/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