Activity for GitForce
-
GitForce released /GitForce/GitForce-1.0.65.exe
-
Goran Devic committed [444a81] on Code
### Release 1.0.65 (2025/11/05)
-
Update license to GPLv3 (was a simple GPL)
-
Fixed a crash on cancel from the initial git list
-
### Release 1.0.64 (2025/08/31)
-
Changed deprecated 'whatchanged' to 'log' argument
-
-
-
### Release 1.0.63 (2025/07/01)
-
Add .NET 4.5 support files and readme
-
Revert .NET update, back to 4.5
-
-
### Release 1.0.62 (2025/07/01)
-
Update readme
-
Update links to documents, now at https://baltazarstudios.com/software/gitforce
-
Update .NET target version from 4.5 to 4.8
-
Update link to git-scm
-
Recognize new Beyond Compare 5 folders
-
-
### Release 1.0.61 (2024/09/07)
-
Changed links from SF to github
-
Add newest putty version 0.81
-
Removed chocolatey build
-
-
### Release 1.0.60 (2023/03/02)
-
Correctly open web pages on Linux
-
Class Exec, set StandardOutputEncoding to UTF8
-
### Release 1.0.59 (2021/12/17)
-
Delete branch add option to remove tracking of a remote branch
-
-
Alex Purins posted a comment on discussion Open Discussion
Workaround found - set "Retrieve last" value to something small (in Settings Options Commits). Slowness was not caused by the large number of files, but a large Revisions list. The formatted git log command in PanelRevlist.UpdateList was very fast when run separately, so slowness is in the processing of its output, which was 1.2MB with 16,935 entries (my other projects are a tenth of that size). Could not quickly see why that panel refresh code was being called on all other panel refreshes (even...
-
Same regardless of right tab, following appears in the Log window immediately, and any changes appear in the Status panel very quickly, then unresponsive to the 16s mark (the git log below, when run at bash command line and redirected to a file, has 16,692 lines, and takes under 2 sec, consistent with Sourcetree's timing): Exec: C:\Program Files\Git\bin\git.exe status --porcelain -uall -z git branch -a Exec: C:\Program Files\Git\bin\git.exe branch -a ...handful of branch names... Exec: C:\Program...
-
Could you open the log window and send me (or attach?) the log after the point of when it's really slow? Depending on the active tab in the right pane, different git commands are issued, and the log will show them.
-
Looking now more closely, the 1.5GB was for the entire project directory, including 1.0GB .git repo subtree, so only 500MB to be Git-checked. And unusual because it is not just sources but also binaries (since production installs are themselves full Git repos), around 450MB (and 9500 of the files) in jarfiles, images, fonts, etc. Leaving around 50MB and 5300 conventional sourcefiles, not unreasonable. So there's probably not much else around like it.
-
Hey Alex, that is a huge project (1.5GB)! I don't think I ever tried it with anything that large. I need to find something sufficiently large, open source repo, to try to repro that lag (do you know of any?), to see where it is choking and if it can be bypassed... Thanks!
-
A new project is taking 16 seconds to refresh the Status panel, where Sourcetree takes under 2 seconds, for 1.54GB in 14,843 files in 1,002 folders (while in smaller existing projects, the Status panel continues to refresh sub-second, eg for 143MB in 2,315 files in 146 folders). So there is something inefficient in how GitForce interacts with Git, or itself checks for differences ? Am using current GitForce 1.0.58, on current Windows 20H2, Lenovo T590, WDC SN720 SSD, with git version 2.23.0.windows.1....
-
-
Catch possible invalid git status code in ViewAssignIcon()
-
### Release 1.0.58 (2020/12/31)
-
When creating new repos, add option to set initial branch name
-
catch possible exception around GetFileNameWithoutExtension
-
Minor adding more logging
-
Linux swap editors
-
Lock status strip
-
Adding Meld to the list of Windows diff tools to recognize
-
Changed email address
-
-
Minor whitespace and EOL cleanup
-
Fix errors on long repo clones
-
Remove ESC[ + single character sequence from the git output
-
### Release 1.0.57 (2020/02/21)
-
Add --repo command line option
-
-
### Release 1.0.56 (2019/11/03)
-
Better handling of missing workspaces
-
Fixed one warning in debug mode compile
-
Fixed the changelist status text
-
-
### Release 1.0.55 (2019/03/24)
-
Update PuTTY for Windows
-
-
-
### Release 1.0.54 (2018/02/24)
-
Fixed setting SecurityProtocolType.Tls12; to also compile on Linux
-
Simple variable name change
-
Rewrote new version check code
-
Updated sourceforge path version check
-
### Release 1.0.53 (2018/02/24)
-
Updated Windows putty helper tools
-
Fixed new version check using new sourceforge SSL site
-
Improve user experience in tree panel (two folder colors + tooltips) (#29)
-
Add missing item to the View dropdown
-
Add option to Warn if started as Admin
-
-
### Release 1.0.52 (2018/01/15)
-
Prevent a fault in the rev history when a file given does not have git history
-
Correctly handle files with spaces in form changelist
-
GitHub committed [530bf8]
Merge pull request #28 from pausan/local-files-view-not-in-gitignore
-
Pau Sanchez committed [424f7c]
Add view on left panel for local files excluding .gitignore
-
GitHub committed [98674f]
Merge pull request #27 from hrotkogabor/slash_in_branchname
-
GitHub committed [43d3f4]
enable slash in branch name
-
Even more additional checks against storing invalid repo column widths
-
### Release 1.0.51 (2017/11/29)
-
Merge branch 'master' of ssh://git.code.sf.net:22/p/gitforce/code
-
Release script remove one empty line in the output
-
-
### Release 1.0.51 (2017/11/29)
-
Removed unnecessary file
-
Fixed repo reordering
-
Additional checks against storing invalid repo column widths
-
-
### Release 1.0.51 (2017/09/17)
-
Release script, copy exe to few places
-
Add readme for chocolatey packager
-
Adding chocolatey package files
-
Updating release script to increment version for chocolatey package
-
Check if the app is run as Admin/Root
-
-
### Release 1.0.49 (2017/09/02)
-
Removing obsolete code that downloads git
1 >
