Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Vsevolod Myalitsin <ub4nal@mail.ru>,
	 ben.knoble@gmail.com, git@vger.kernel.org,  gitster@pobox.net
Subject: Re: [PATCH v4 2/3] advice: introduce advice scoping mechanism
Date: Thu, 22 Oct 2026 13:56:38 -0700	[thread overview]
Message-ID: <xmqqtsmde9o9.fsf@gitster.g> (raw)
In-Reply-To: <20260917132540.GA101514@peff.net> (Jeff King's message of "Thu, 17 Sep 2026 09:25:40 -0400")

Jeff King <peff@peff.net> writes:

> On Thu, Sep 17, 2026 at 05:03:50PM +0300, Vsevolod Myalitsin wrote:
>
>> Junio C Hamano writes:
>> > So to conclude the topic, we would only need this?
>> 
>> Yes, I think this is indeed where we were heading.
>
> Likewise, and the patch looks good to me from a quick read.
>
>> However, during the discussion I really liked the idea of passing a
>> pointer to the "advice_setting" to "vadvise()" instead of passing its
>> individual fields. It seems like a cleaner interface, even though it
>> is not directly related to this fix.
>> 
>> Would it make sense to submit that change as a separate patch?
>
> I think so. I probably would not have looked into it as a cleanup on its
> own, but since we already spent time thinking about it, let's not waste
> those brain cycles.

So I should mark jc/advice-config-set-global for 'next' and Vsevolod
can look into cleaning up the API as an independent effort?


  reply	other threads:[~2026-10-22 20:56 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2027-08-29  0:49 [PATCH v3] advice: use global config for default branch name Vsevolod Myalitsin
2026-09-09 20:27 ` Jeff King
2026-09-09 21:21   ` Junio C Hamano
2026-09-09 21:22   ` Vsevolod Myalitsin
2026-09-09 22:46     ` Jeff King
2026-09-10  4:43       ` Vsevolod Myalitsin
2026-09-09 20:50 ` Junio C Hamano
2026-09-09 21:30   ` Vsevolod Myalitsin
2026-09-09 22:31     ` Junio C Hamano
2026-09-10  8:53 ` [PATCH v4 0/3] defaultBranchName advice is useless Vsevolod Myalitsin
2026-09-10  8:53   ` [PATCH v4 1/3] advice: pass the entire advice_setting to vadvise() Vsevolod Myalitsin
2026-09-10 17:43     ` SZEDER Gábor
2026-09-10  8:53   ` [PATCH v4 2/3] advice: introduce advice scoping mechanism Vsevolod Myalitsin
2026-09-10 15:36     ` Junio C Hamano
2026-09-10 15:52       ` Jeff King
2026-09-10 17:54         ` Vsevolod Myalitsin
2026-09-10 19:05           ` Jeff King
2026-09-10 18:35         ` Junio C Hamano
2026-09-10 19:03           ` Jeff King
2026-09-10 19:54             ` Junio C Hamano
2026-09-10 20:11               ` Jeff King
2026-09-10 20:25                 ` Junio C Hamano
2026-09-12  8:12                   ` Vsevolod Myalitsin
2026-09-13 16:32                     ` Junio C Hamano
2026-09-14 17:00                       ` Jeff King
2026-09-14 19:53                         ` Junio C Hamano
2026-09-14 22:01                           ` Junio C Hamano
2026-09-17 14:03                             ` Vsevolod Myalitsin
2026-09-17 13:25                               ` Jeff King
2026-10-22 20:56                                 ` Junio C Hamano [this message]
2026-09-10  8:53   ` [PATCH v4 3/3] advice: use global config for default branch name Vsevolod Myalitsin
2026-10-24  5:32 ` [PATCH v3] " David Timber

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=xmqqtsmde9o9.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.net \
    --cc=peff@peff.net \
    --cc=ub4nal@mail.ru \
    /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