linux-kernel - Re: [mISDN PATCH v2 00/19] mISDN patchset for next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20090525.005311.249649223.davem@davemloft.net>
Date:	Mon, 25 May 2009 00:53:11 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	keil@...systems.de
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	i4ldeveloper@...tserv.isdn4linux.de
Subject: Re: [mISDN PATCH v2 00/19] mISDN patchset for next

From: Karsten Keil <keil@...systems.de>
Date: Fri, 22 May 2009 22:42:47 +0200

> This is a update of the mISDN driver for net-next.
> It syncs the mISDN driver with the development on git.misdn.org.
> More updates (new hardware support) will follow.
> 
> You can pull it from 
> git://master.kernel.org/pub/scm/linux/kernel/git/kkeil/ISDN-2.6-net-next.git for_dave
> 
> Andreas Eversberg (12):
>   Add watchdog functionality to hfcmulti driver
>   DSP now uses ring buffer for echo canceler

There is no way I'm pulling from that tree, even with the fixed
up patch #9.

How in the world is anyone supposed to know these are mISDN changes
by looking at those changlog header lines?  They say nothing about
the subsystem they are in.

I've modified every commit log message so that it says:

mISDN: foo bar baz

instead of the anonymous stuff above.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/