FUTURE POSTS
- Partial writes, IO_Uring and safety - about one day from now
- Configuration values & Escape hatches - 4 days from now
- What happens when a sparse file allocation fails? - 6 days from now
- NTFS has an emergency stash of disk space - 8 days from now
- Challenge: Giving file system developer ulcer - 11 days from now
And 4 more posts are pending...
There are posts all the way to Feb 17, 2025
Comments
Are you using Windows 7?
Heh who said new version control system must be better than the old one? You have exchanged known annoyances for a bunch of new ones
Yeah, git-gui and gitk do hang every now and then (at least on Windows). There's no perfect gui (yet) but I'm currently settling for a mix of git-gui (with several custom "tools"), gitk and TortoiseGit. Especially TortoiseGit's rebase is great.
The Windows support for Git is very much an afterthought so you are better off sticking to the command line tools. I doubt the situation will improve much until we get a version written with Windows support in mind (maybe GitSharp when it matures?)
Even with the problems of using Git on Windows it is still my favorite SCM tool :)
Don't use a gui, none is good enough, I found command line to be very easy to work with git.
I do a lot of git from the command line too, since so many actions are just one command - it is well worth the effort to learn them.
Yea, wish sucks in windows. This is probably the biggest issue w/ git in windows. That said, it's fairly infrequent and you can safely end task and relaunch... annoying but it's not keeping you from doing your work (like waiting for a remote diff)
Comment preview