list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: Johannes Schindelin <>
To: Jeff King <>
Cc: Junio C Hamano <>,
Subject: js/early-config-with-onbranch, was Re: What's cooking in git.git (Aug 2019, #01; Thu, 1)
Date: Fri, 2 Aug 2019 14:12:34 +0200 (CEST)
Message-ID: <> (raw)
In-Reply-To: <>

Hi Peff,

On Thu, 1 Aug 2019, Jeff King wrote:

> On Thu, Aug 01, 2019 at 01:05:12PM -0700, Junio C Hamano wrote:
> > * js/early-config-with-onbranch (2019-07-31) 1 commit
> >   (merged to 'next' on 2019-08-01 at 26b713c824)
> >  + config: work around bug with includeif:onbranch and early config
> >
> >  The recently added [includeif "onbranch:branch"] feature does not
> >  work well with an early config mechanism, as it attempts to find
> >  out what branch we are on before we even haven't located the git
> >  repository.  The inclusion during early config scan is ignored to
> >  work around this issue.
> >
> >  Will merge to 'master'.
> I had some open comments here on how the "do we have a repo" check is
> done, but I think what is committed here is functionally equivalent. I
> can pursue the NULL the_repository cleanups separately.

Right, I read that as "maybe later" comments, as that project is so
different from trying to fix the `onbranch` feature with regards to the
early config machinery.

Or did I misread and you want me to do anything about it before v2.23.0?


  reply	other threads:[~2019-08-02 12:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 20:05 Junio C Hamano
2019-08-01 21:42 ` Jeff King
2019-08-02 12:12   ` Johannes Schindelin [this message]
2019-08-02 18:38     ` js/early-config-with-onbranch, was " Jeff King
2019-08-02 16:23   ` Junio C Hamano
2019-08-02 12:06 ` js/visual-studio, was " Johannes Schindelin
2019-08-02 16:42   ` Junio C Hamano
2019-08-03 20:22     ` Johannes Schindelin
2019-08-05 18:40       ` Junio C Hamano

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ \
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for the project(s) associated with this inbox:

AGPL code for this site: git clone