linux-kernel - Re: [GIT PULL] x86/entry for 7.0-rc1

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: <aYzHabdjASuLFRSf@black.igk.intel.com>
Date: Wed, 11 Feb 2026 19:16:09 +0100
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>, Peter Anvin <hpa@...or.com>,
	x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] x86/entry for 7.0-rc1

On Tue, Feb 10, 2026 at 08:24:49PM -0800, Linus Torvalds wrote:
> On Mon, 9 Feb 2026 at 13:09, Dave Hansen <dave.hansen@...ux.intel.com> wrote:

...

> Maybe some people keep their build trees religiously clean or entirely
> separate from their source trees. But I certainly don't, and I know
> many other developers don't.

There may be actual benefits of having source and output not to be mixed.
For example, it can be that one has a source on an read-only volume or
by a network filesystem. It's possible to say that cloning a Git repository
locally is the solution, but for some cases it might be too much.

And yes, I happily use `git worktree`. The difference with worktree and
output folder, that the output may be located on tmpfs or be removed w/o
much thinking of unfinished jobs or so.

-- 
With Best Regards,
Andy Shevchenko