Philippe Miossec
Philippe Miossec
@pmgiant to fix the build, run the script update-loc.cmd that you will find at the repository root folder.
> As suggested above by "mstv", I created a new "fixup!..." commit instead of squashing consecutive tiny code refactorings. Now the "block-fixup" check fails. fixup are intended to be temporary...
Seems similar to #11387. Please have a look.
I will add that you can open the "command log" window (F12) before launching the history and have a look at the git log command to see if that is...
Duplicate of #9648 I think. None of the dev team members successfully reproduce. it needs to be debugged by someone who have the issue...
@RussKie 1. In this line https://github.com/gitextensions/gitextensions/blob/master/GitUI/GitExtensionsForm.cs#L133 , I have the feeling that `DesktopLocation` is wrong and that should be `Location` like in the `else` because we are checking that the...
> It will be most helpful to me to have these additions in the lower pane of the dialog (green arrows). This can be looked up without closing the merge...
> I would prefer to have the branch name where available, then commit, then remote/incoming (keep ours/theirs as it is used by Git). I keep that in mind for later...
It will require a little more investigation on your part to really understand the issue (using task manager or process explorer): * Are exactly the same exe launched? * if...
> Running the first command from powershell shows the same behavior as the manual run - everything works as expected. So, probably, some wizzardy is happening on the VS side....