From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Peter Anvin <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] x86/entry for 7.0-rc1
Date: Wed, 11 Feb 2026 19:16:09 +0100 [thread overview]
Message-ID: <aYzHabdjASuLFRSf@black.igk.intel.com> (raw)
In-Reply-To: <CAHk-=whVY4mq1Fd=Vhwy0dK8fR5cOLkiy1OZMG4QyEMaGEd9ZQ@mail.gmail.com>
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@linux.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
next prev parent reply other threads:[~2026-02-11 18:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 21:09 [GIT PULL] x86/entry for 7.0-rc1 Dave Hansen
2026-02-11 3:57 ` pr-tracker-bot
2026-02-11 4:24 ` Linus Torvalds
2026-02-11 4:39 ` Linus Torvalds
2026-02-11 6:15 ` H. Peter Anvin
2026-02-11 6:34 ` Linus Torvalds
2026-02-11 16:30 ` H. Peter Anvin
2026-02-11 17:05 ` Linus Torvalds
2026-02-11 17:39 ` H. Peter Anvin
2026-02-11 17:52 ` Linus Torvalds
2026-02-11 19:22 ` H. Peter Anvin
2026-02-11 18:16 ` Andy Shevchenko [this message]
2026-02-11 18:35 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aYzHabdjASuLFRSf@black.igk.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox