linux-kernel - linux-next: strange state of the kbuild tree

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

Message-Id: <20140408074734.34deb43270183941b5118c7f@canb.auug.org.au>
Date:	Tue, 8 Apr 2014 07:47:34 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Michal Marek <mmarek@...e.cz>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: linux-next: strange state of the kbuild tree

Hi Michal,

I noticed that you have two copies of two commits in your tree ("Kbuild,
lto: Set TMPDIR for LTO v4" and "Kbuild, lto: Add Link Time Optimization
support v3").  I understan why you recommitted them (to add your
Signed-off-by), but to leave the unsigned commits in there sort of
defeats the purpose.  This is probably a case where you should have
removed the original merge (or just these two commits) and then merged
the new version.

I am not sure what you intend to send to Linus, but this whole tree (in
one piece) should not be it.  From the state of the tree, it looks like
you send your separate topic branches (or a new merge of them) which
should be ok, but please after doing that, clean up your for-next branch
(it current has merge commits dating back to May, 2103 in it).
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped