From: Luis Chamberlain <mcgrof@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Boris Kolpackov <boris@codesynthesis.com>,
Johannes Berg <johannes@sipsolutions.net>,
Felix Fietkau <nbd@openwrt.org>,
Patrick Franz <patfra71@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Junio C Hamano <gitster@pobox.com>,
linux-kernel@vger.kernel.org
Subject: Re: kconfig as a git subtree on Linux
Date: Thu, 26 Nov 2020 15:33:49 +0000 [thread overview]
Message-ID: <20201126153349.GK4332@42.do-not-panic.com> (raw)
In-Reply-To: <20201126091329.GA21541@infradead.org>
On Thu, Nov 26, 2020 at 09:13:29AM +0000, Christoph Hellwig wrote:
> On Wed, Nov 25, 2020 at 05:25:44PM +0000, Luis Chamberlain wrote:
> > I'd like to propose we discuss the possibility of taking kconfig and
> > making it a git subtree under the Linux kernel. This would allow
> > other projects outside of the Linux kernel to be able to update their
> > own copy / fork of kconfig in a jiffie *very* easily.
>
> Hell no. Not because I'm against sharing, but because git submodules
> are a complete fucking pain to deal with. Adding submodules just fucks
> up being able to easily use a repository.
I agree wholeheartedly! But I was not alking about git submodules. I
think git submodules should be taken to the back of an alley and shot.
But, git subtrees, however, now that is proving to me to be very sexy.
Luis
next prev parent reply other threads:[~2020-11-26 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 17:25 kconfig as a git subtree on Linux Luis Chamberlain
2020-11-26 9:13 ` Christoph Hellwig
2020-11-26 15:33 ` Luis Chamberlain [this message]
2020-11-26 10:38 ` Boris Kolpackov
2020-11-26 15:38 ` Luis Chamberlain
2020-11-28 8:39 ` Masahiro Yamada
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=20201126153349.GK4332@42.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=acme@redhat.com \
--cc=boris@codesynthesis.com \
--cc=gitster@pobox.com \
--cc=hch@infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mingo@kernel.org \
--cc=nbd@openwrt.org \
--cc=patfra71@gmail.com \
/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).