Re: RFC: How should we handle un-deleted remote branches?

2018-04-22 Thread Ævar Arnfjörð Bjarmason
On Sun, Apr 22 2018, Andreas Heiduk wrote: > Am 22.04.2018 um 13:17 schrieb Ævar Arnfjörð Bjarmason: >> >> On Sun, Apr 22 2018, Andreas Heiduk wrote: >> >>> Am 20.04.2018 um 14:14 schrieb Ævar Arnfjörð Bjarmason: But this is a possible work-around: git init /tmp/empty.git

Re: RFC: How should we handle un-deleted remote branches?

2018-04-22 Thread Andreas Heiduk
Am 22.04.2018 um 13:17 schrieb Ævar Arnfjörð Bjarmason: > > On Sun, Apr 22 2018, Andreas Heiduk wrote: > >> Am 20.04.2018 um 14:14 schrieb Ævar Arnfjörð Bjarmason: >>> But this is a possible work-around: >>> >>> git init /tmp/empty.git >>> git remote add avar file:///tmp/empty.git >>>

Re: RFC: How should we handle un-deleted remote branches?

2018-04-22 Thread Ævar Arnfjörð Bjarmason
On Sun, Apr 22 2018, Andreas Heiduk wrote: > Am 20.04.2018 um 14:14 schrieb Ævar Arnfjörð Bjarmason: >> But this is a possible work-around: >> >> git init /tmp/empty.git >> git remote add avar file:///tmp/empty.git >> git remote prune avar >> git remote remove avar > > This won't

Re: RFC: How should we handle un-deleted remote branches?

2018-04-22 Thread Andreas Heiduk
Am 20.04.2018 um 14:14 schrieb Ævar Arnfjörð Bjarmason: > But this is a possible work-around: > > git init /tmp/empty.git > git remote add avar file:///tmp/empty.git > git remote prune avar > git remote remove avar This won't do it also? git remote prune origin > I

RFC: How should we handle un-deleted remote branches?

2018-04-20 Thread Ævar Arnfjörð Bjarmason
I removed a remote and its refs persisted. At first I thought this was a bug but looking at add_branch_for_removal()'s "don't delete a branch if another remote also uses it" logic it's intentional. This goes very wrong if you do e.g.: ( rm -rf /tmp/git && git clone --bare