linux-kernel - Re: Please pull

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: <m31vyk4kde.fsf@maximus.localdomain>
Date:	Mon, 13 Oct 2008 16:53:17 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Please pull - generic HDLC

Adrian Bunk <bunk@...nel.org> writes:

> The over 3 weeks old -next already contains mostly the same as the HDLC 
> tree contains now.
>
> The thing you two should sort out is why the tree ended up as an own 
> tree in -next instead of pull requests to David long ago.
>
> E.g. the netdev and wireless trees also don't go into -next, but instead 
> with frequent pull requests to David.

I can't see any problem with this, is there any?

I want the HDLC tree tested in next before it's merged upstream
(= David's tree(s)). I don't want to push crap upstream  first and
only then try to fix it (though a bug still slips in sometimes).
-- 
Krzysztof Halasa
--
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/