From: Linus Torvalds <torvalds@linux-foundation.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [GIT PULL] Kbuild updates for v6.3-rc1
Date: Mon, 27 Feb 2023 09:25:54 -0800 [thread overview]
Message-ID: <CAHk-=wgM-W6Fu==EoAVCabxyX8eYBz9kNC88-tm9ExRQwA79UQ@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wh5AixGsLeT0qH2oZHKq0FLUTbyTw4qY921L=PwYgoGVw@mail.gmail.com>
On Mon, Feb 27, 2023 at 9:08 AM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> So here's the simple rule: if the packaging people can't be bothered
> to use "gti archive" to make their packages, then they had better just
> do a "make clean" first (or, better yet, do "git clean -dqfx" to
> really clean up, because "make clean" isn't 100% reliable either).
>
> We don't add more broken infrastructure to deal with broken workflows.
> Just do the right thing.
Note: I'm perfectly happy to just revert this, but if I have to do it,
then pretty much _all_ the packaging changes get reverted, because I'm
not going to be able to figure out which parts don't rely on the new
broken script.
So I'd rather take a more directed revert from you. Or, better yet,
just a rewrite to do the right thing (ie "git archive").
Because really - any distro packager had better have the git tree.
Linus
next prev parent reply other threads:[~2023-02-27 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 16:33 [GIT PULL] Kbuild updates for v6.3-rc1 Masahiro Yamada
2023-02-26 18:58 ` Linus Torvalds
2023-02-27 10:09 ` Masahiro Yamada
2023-02-27 17:08 ` Linus Torvalds
2023-02-27 17:25 ` Linus Torvalds [this message]
2023-02-28 16:21 ` Masahiro Yamada
2023-02-28 16:19 ` Masahiro Yamada
2023-02-26 20:40 ` pr-tracker-bot
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='CAHk-=wgM-W6Fu==EoAVCabxyX8eYBz9kNC88-tm9ExRQwA79UQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@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;
as well as URLs for NNTP newsgroup(s).