linux-kernel - Re: [1/3] gigaset: avoid registering CAPI driver more than once

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100315.142040.58983190.davem@davemloft.net>
Date:	Mon, 15 Mar 2010 14:20:40 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	isdn@...ux-pingi.de
Cc:	tilman@...p.cc, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	isdn4linux@...tserv.isdn4linux.de, hjlipp@....de,
	i4ldeveloper@...tserv.isdn4linux.de
Subject: Re: [1/3] gigaset: avoid registering CAPI driver more than once

Karsten the way you reforward patches does not work.

And I've told you about this last time you submitted ISDN patches.

You don't add an extra "From: " line in the message body, so when the
patch gets applied the author gets set to _you_ instead of the person
who actually wrote the change.

All you're doing is ACK'ing this person's work, so simply reply to the
patch they posted and with your "Acked-by" line.  This way patchwork
and friends will figure out the rest when the patch gets integrated
into the net-2.6 tree.

By reposting the patches the way you are we're losing information.

Add to this the fact that you never have the time to properly take
care of ISDN patches, and when you do finally "get to it" you make all
kinds of submission errors.

This is not the first time either, it happens over and over again.
It's incredibly frustrating, especially for me.

Please seriously consider handing ISDN maintainership over to someone
who unlike you 1) has the time and the desire and 2) knows how to
submit patches properly.  Probably Tilman is the person who most meets
these criteria based upon what I've seen.

Meanwhile, I'm going to apply the original patches as posted by
Tilman so that the proper authorship gets set.
--
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/