Hi Stefan & Jason,
On Tue, 27 Mar 2018, Stefan Beller wrote:
> On Tue, Mar 27, 2018 at 1:41 PM Jason Frey wrote:
>
> > at which point you can see the duplicate sections (even though one is
> > empty). Also note that if you do the steps again, you will be left
> > with 3 sections, 2 of which ar
From: "Ævar Arnfjörð Bjarmason"
On Tue, Mar 27 2018, Jason Frey wrote:
While the impact of this bug is minimal, and git itself is not
affected, it can affect external tools that want to read the
.git/config file, expecting unique section names.
To reproduce:
Given the following example .git/
From: "Ævar Arnfjörð Bjarmason"
On Tue, Mar 27 2018, Jason Frey wrote:
While the impact of this bug is minimal, and git itself is not
affected, it can affect external tools that want to read the
.git/config file, expecting unique section names.
To reproduce:
Given the following example .git/
From: "Ævar Arnfjörð Bjarmason"
On Tue, Mar 27 2018, Jason Frey wrote:
While the impact of this bug is minimal, and git itself is not
affected, it can affect external tools that want to read the
.git/config file, expecting unique section names.
To reproduce:
Given the following example .git/
From: "Ævar Arnfjörð Bjarmason"
On Tue, Mar 27 2018, Jason Frey wrote:
While the impact of this bug is minimal, and git itself is not
affected, it can affect external tools that want to read the
.git/config file, expecting unique section names.
To reproduce:
Given the following example .git/
On Tue, Mar 27 2018, Jason Frey wrote:
> While the impact of this bug is minimal, and git itself is not
> affected, it can affect external tools that want to read the
> .git/config file, expecting unique section names.
>
> To reproduce:
>
> Given the following example .git/config file (I am leavi
On Tue, Mar 27, 2018 at 1:41 PM Jason Frey wrote:
> at which point you can see the duplicate sections (even though one is
> empty). Also note that if you do the steps again, you will be left
> with 3 sections, 2 of which are empty. This process can be repeated
> over and over.
I agree that thi
While the impact of this bug is minimal, and git itself is not
affected, it can affect external tools that want to read the
.git/config file, expecting unique section names.
To reproduce:
Given the following example .git/config file (I am leaving out the
[core] section for brevity):
[remote
8 matches
Mail list logo
