netdev - Re: [PATCH] allow VLAN interface on top of bridge interface

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: <20070412.145945.124891857.davem@davemloft.net>
Date:	Thu, 12 Apr 2007 14:59:45 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	akpm@...ux-foundation.org
Cc:	netdev@...r.kernel.org, j.borsboom@...smusmc.nl,
	greearb@...delatech.com
Subject: Re: [PATCH] allow VLAN interface on top of bridge interface

This is the second time this patch has been forwarded to netdev
in the past hour.

And I'll say the same thing I said to the first person who did it this
way.  Because you just blindly forwarded this here, and did not tell
the orignal poster why, and furthermore took linux-kernel off the CC
list, we now have two problems:

1) The poster hasn't learned where the correct location is
   to send the report and why that is the correct place.
   They just see their report getting forwarded around.

2) Since linux-kernel got dropped, people will reply to both
   instances of the original posting, so people watching the
   thread one on side will miss the postings made on the
   other.

I'd appreciate it if the poster were explicitly informed of where
they should send their report as well as retaining linux-kernel
on the CC: list if forwarding to netdev as well so we can avoid
both of these problems.

Thanks.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html