While git will likely always need some bits of Linux abstraction because how much of it's "high level" is written in Bash shell scripts and random bits of awk / sed / perl, it certainly seems that the low level stuff is less reliant on Linux abstraction than ever and is increasingly cross-platform-intended C. Since Microsoft has taken an active role in git development, and especially since the Windows team itself switched to git, the official Git for Windows install and support for that install has been really good. I believe it is still better because you don't rely on MinGW or some other Linux abstraction layer (though it uses python). > It had better windows support than Git did for a long time. It was also a relatively short-lived fork as it did merge upstream. The file system changes were extremely low level and likely couldn't have been handled with extension hooks in Hg either (some of it, from what I read of it, would be more like the equivalent of changing the Python standard library, specifically the OS and file-system-specific bits, underneath Hg than changes to Hg or its extensions). So I could create an extension that completely changes some aspect of how Mercurial works without needing to fork it (unlike Git, where Microsoft had to release a fork of it to support their file system change). If a company (such as Google or Facebook) wants to change the behavior of an action, they can override or hook into a specific spot in the code and change how things work. Whenever they update/revert to another revision/branch the binaries/assets download automatically anyway. Devs also have to deal with more disk space being used, but a) storage is cheap and b) it is trivial to clear old binaries/assets from their disk on an automated schedule. Sure, you greatly increase the size of a repo on whatever machines are serving it, but storage is cheap these days so who cares. We implemented this with a combination of Mercurial's first-party "largefiles" extension, high compression of our binaries/assets (via 7z), and a variety of scripts/hooks to (de)compress the relevant files whenever `hg commit`, `hg up`, `hg revert`, etc. We needed some of the projects in our repos to be fully compilable against any binaries/assets at any point in time in the repo's complete history. Mercurial, at least in the early days, had much better support (IMHO) for large/binary files than git (perhaps git is on-par now, not sure). Mercurial's hooks have made a wide variety of automatic tasks much easier to systematize across all our repos for any repo-related action that any dev makes. Needless to say, this is all very strange.We use the hell out of this at my company. Sometimes it works and sometimes it doesn't. Oddly, he is getting erratic results with his configuration (which looks very much like mine). There is another person in my group that is bringing up a Mac and has downloaded the trial version of BC. I also verified that bcomp was not running with 'ps -A | grep "bcomp"' (I actually didn't think of this for Tortoise, but the validation through the Force Quite menu should be sufficient). I verified this closure by ensuring that the application disappeared from the 'Force Quit' menu. However, neither case changes the net result of being unable to compare two versions of a file.Īfter saving my config file changes, I reloaded the changes and then closed TorgoiseHG. However, using the other "how to get BC to work" thread as a basis, I placed both before and after the block. The block of code provided in post #7 is missing the block so I wasn't sure where to put it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |