johnddx

This issue hinders me frequently. If I'm comparing {a, b, d} and {a, b, c, d}, the useful difference is "c" (or first mismatch is "c" != "d"). Telling me...

Looks like I've gone through a few dev builds, so I would wager I did hit #6783, that might be how I saw it first a couple of weeks ago....

It has now happened again a 3rd time, the second time on the original machine, with: - Git Extensions 3.2.1.6628 - Build bc07663c3c893f1d896520e0bdcfbe35cfe4b729 - Git 2.22.0.vfs.1.1.57.gbaf16c8 - Microsoft Windows NT...

As an experiment, I tried closing GitEx and moving the 7k settings files so that it had to recreate them from scratch. The new files are 6k, largely identical to...

Closed by mistake.

I'm concerned that it would delete branches that are not contained by another branch. (the remote deletion could have been a de-publishing act, rather than an indication that the branch...

Okay yes, there are actually several problems with "git fetch --prune": ~~1. "git fetch --prune" will remove branches that are not merged. If you push a branch, and a colleague...

I struck through most of my previous comment, because it was misguided. The real problem with "git fetch --prune" is that it will _only_ delete remote refs. It will never...

> > As such, git-up.fetch.prune should not even be an option, it should just be the only behavior. > > Unfortunately we can't change this without breaking compatibiltiy with the...

> Interesting, how did you come to this conclusion? According to the internet (http://blag.ahax.de/post/421939327/recovering-a-deleted-branch-using-git-reflog) and my own (admittedly quick) test git actually should keep the reflog for deleted branches. What...