From: Taylor Blau <firstname.lastname@example.org> To: Derrick Stolee <email@example.com> Cc: "Derrick Stolee via GitGitGadget" <firstname.lastname@example.org>, email@example.com, Johannes.Schindelin@gmx.de, firstname.lastname@example.org, "Junio C Hamano" <email@example.com>, "Jakub Narębski" <firstname.lastname@example.org>, "Nguyễn Thái Ngọc Duy" <email@example.com>, "Carlo Marcelo Arenas Belón" <firstname.lastname@example.org>, "Ævar Arnfjörð Bjarmason" <email@example.com> Subject: Re: [PATCH v3 0/3] [RFC] Create 'core.featureAdoptionRate' setting to update config defaults Date: Tue, 9 Jul 2019 13:55:52 -0500 [thread overview] Message-ID: <20190709185552.GA84865@TaylorsMBP6986.attlocal.net> (raw) In-Reply-To: <firstname.lastname@example.org> Hi Derrick, I'm a little bit late to the part, but I think that this is a really interesting feature with a lot of really interesting discussion so far. I hope you don't mind me throwing in my $.02 as well :-). On Mon, Jul 08, 2019 at 03:22:49PM -0400, Derrick Stolee wrote: > On 7/1/2019 10:29 AM, Derrick Stolee via GitGitGadget wrote: > > Here is a second run at this RFC, which aims to create a "meta" config > > setting that automatically turns on other settings according to a user's > > willingness to trade new Git behavior or new feature risk for performance > > benefits. The new name for the setting is "core.featureAdoptionRate" and is > > an integer scale from 0 to 10. There will be multiple "categories" of > > settings, and the intention is to allow more granular levels as necessary. > > (Adding people who contributed feedback to CC line.) > > It seems that this "Feature Adoption Rate" idea was too simplistic, and > had several issues. Time to take a different stab at this direction, but > with these clear goals in mind: > > 1. We want intermediate users to be able to take advantage of new config > options without watching every release for new config options. > > 2. The config name should match the general effect of the implied > settings. > > 3. There are orthogonal settings that may not apply beneficially to > all repos. I think that this is a clear representation of the initial reaction I had to the 'core.featureAdoptionRate' idea. I had drafted a response to advance these concerns before realizing that this subsequent RFC existed, which does a nice job highlighting the concerns that I had. > With this in mind, I propose instead a set of "feature.*" config settings > that form groups of "community recommended" settings (with some caveats). > In the space below, I'll list a set of possible feature names and the > implied config options. I think that 'feature.*' configuration settings are a good idea. They address each of the above (3) concerns, since they are: 1. Can be easily adopted by even novice-level users. Perhaps novice-users will not be setting 'feature.manyFiles = 1', but they can easily opt-in to organization-level features that have been defined to handle organization-specific concerns. 2. This one is straightforward: I think that setting 'feature.manyFiles = 1' is clearer than 'feature.adoptionRate = 3'. 3. Right. Windows developers may have a different set of what features are interesting to adopt than, say, every-day users, and likewise for kernel developers, too. > First, the main two categories we've discussed so far: many commits and > many files. These two feature sets are for when your repo is large in > one of these dimensions. Perhaps there are other settings to include > in these? > > feature.manyFiles: > index.version = 4 > index.threads = true > core.untrackedCache = true > > feature.manyCommits: > core.commitGraph = true > gc.writeCommitGraph = true > (future: fetch.writeSplitCommitGraph = true) I think that for this *feature* (pun mostly unintended) to really shine, we ought to adopt Junio's suggestion in  that we allow users to: * use pre-baked features that are defined within and shipped with Git itself. * define their own features and second-order features that can reference both pre-baked and user-defined feature groups. I think that this will let, say, folks at Microsoft to define a set of features that are interesting to Windows developers, that are separate from the features that core Git thinks will be interesting to every-day users. > > <snip> > > Thanks, > -Stolee Thanks, Taylor : https://email@example.com/
next prev parent reply other threads:[~2019-07-09 18:55 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-03 20:18 [PATCH 00/11] [RFC] Create 'core.size=large' " Derrick Stolee via GitGitGadget 2019-06-03 20:18 ` [PATCH 01/11] repo-settings: create repo.size=large setting Derrick Stolee via GitGitGadget 2019-06-03 20:42 ` Jeff Hostetler 2019-06-03 20:18 ` [PATCH 03/11] repo-settings: pack.useSparse=true Derrick Stolee via GitGitGadget 2019-06-03 20:18 ` [PATCH 02/11] repo-settings: use index.version=4 by default Derrick Stolee via GitGitGadget 2019-06-03 20:18 ` [PATCH 04/11] status: add status.aheadbehind setting Jeff Hostetler via GitGitGadget 2019-06-03 20:18 ` [PATCH 05/11] status: add warning when a/b calculation takes too long for long/normal format Jeff Hostetler via GitGitGadget 2019-06-03 20:18 ` [PATCH 06/11] status: ignore status.aheadbehind in porcelain formats Jeff Hostetler via GitGitGadget 2019-06-03 20:18 ` [PATCH 07/11] repo-settings: status.aheadBehind=false Derrick Stolee via GitGitGadget 2019-06-03 20:18 ` [PATCH 08/11] fetch: add --[no-]show-forced-updates argument Derrick Stolee via GitGitGadget 2019-06-03 20:18 ` [PATCH 10/11] pull: add --[no-]show-forced-updates passthrough to fetch Derrick Stolee via GitGitGadget 2019-06-03 20:18 ` [PATCH 09/11] fetch: warn about forced updates after branch list Derrick Stolee via GitGitGadget 2019-06-03 20:18 ` [PATCH 11/11] repo-settings: fetch.showForcedUpdates=false Derrick Stolee via GitGitGadget 2019-06-03 20:55 ` [PATCH 00/11] [RFC] Create 'core.size=large' setting to update config defaults Derrick Stolee 2019-06-04 14:43 ` Johannes Schindelin 2019-06-04 14:56 ` Derrick Stolee 2019-06-05 20:39 ` Junio C Hamano 2019-06-06 12:23 ` Derrick Stolee 2019-06-06 16:07 ` Junio C Hamano 2019-06-19 15:11 ` [PATCH v2 0/3] [RFC] Create 'core.featureAdoptionRate' " Derrick Stolee via GitGitGadget 2019-06-19 15:12 ` [PATCH v2 1/3] repo-settings: create core.featureAdoptionRate setting Derrick Stolee via GitGitGadget 2019-06-28 20:50 ` Junio C Hamano 2019-06-28 21:08 ` Derrick Stolee 2019-06-28 21:42 ` Junio C Hamano 2019-06-29 1:43 ` Derrick Stolee 2019-06-30 18:35 ` Carlo Arenas 2019-07-01 12:45 ` Derrick Stolee 2019-07-02 10:47 ` Ævar Arnfjörð Bjarmason 2019-07-02 11:09 ` Duy Nguyen 2019-07-02 14:54 ` Derrick Stolee 2019-07-02 16:59 ` Junio C Hamano 2019-06-19 15:12 ` [PATCH v2 2/3] repo-settings: use index.version=4 by default Derrick Stolee via GitGitGadget 2019-06-19 15:12 ` [PATCH v2 3/3] repo-settings: pack.useSparse=true Derrick Stolee via GitGitGadget 2019-07-01 14:29 ` [PATCH v3 0/3] [RFC] Create 'core.featureAdoptionRate' setting to update config defaults Derrick Stolee via GitGitGadget 2019-07-01 14:29 ` [PATCH v3 1/3] repo-settings: create core.featureAdoptionRate setting Derrick Stolee via GitGitGadget 2019-07-01 23:27 ` Carlo Arenas 2019-07-02 9:20 ` Duy Nguyen 2019-07-02 10:53 ` Ævar Arnfjörð Bjarmason 2019-07-04 22:47 ` Jakub Narebski 2019-07-01 14:29 ` [PATCH v3 2/3] repo-settings: use index.version=4 by default Derrick Stolee via GitGitGadget 2019-07-01 14:29 ` [PATCH v3 3/3] repo-settings: pack.useSparse=true Derrick Stolee via GitGitGadget 2019-07-08 19:22 ` [PATCH v3 0/3] [RFC] Create 'core.featureAdoptionRate' setting to update config defaults Derrick Stolee 2019-07-09 18:55 ` Taylor Blau [this message] 2019-07-09 19:21 ` Junio C Hamano 2019-07-09 19:45 ` Derrick Stolee 2019-07-09 22:05 ` Junio C Hamano 2019-07-22 12:10 ` Derrick Stolee 2019-07-11 21:54 ` Jakub Narebski
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190709185552.GA84865@TaylorsMBP6986.attlocal.net \ --firstname.lastname@example.org \ --cc=Johannes.Schindelin@gmx.de \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v3 0/3] [RFC] Create '\''core.featureAdoptionRate'\'' setting to update config defaults' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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 read-only IMAP folder(s) and NNTP newsgroup(s).