solineu.blogg.se

1. Linux smartgit pro#
2. Linux smartgit software#
3. Linux smartgit code#
4. Linux smartgit password#
5. Linux smartgit windows#

Running locally can be 1000 times faster. Switching from SSHFS to SMB sped up by factor of 0.6 to 5 Switching from WiFi to wired sped SMB up by a factor of 10, and SSHFS

On local system (Ubuntu w 8-core AMD processor and flash storage):

Linux smartgit pro#

On local system (Recent 6-core Macbook Pro with flash storage): 0.210s SSHFS networked file system over wired 1000BASE-T: 17 seconds SSHFS networked file system over WiFi (100BASE-T speeds): 87 seconds SMB networked file system over wired 1000BASE-T: 5 seconds (ditto) SMB networked file system over WiFi (100BASE-T speeds): 55 seconds Times to execute "git status" on the same repo (run repeatedly): If that's true with the native git, then I can't really expect SmartGit to be faster. A simple "git status" could take 80+ seconds (it once took almost five minutes). I found that working on shared file systems slows things down by a factor of 100 or more. I did some testing of git command-line performance, locally and networked. (FYI, here's an email I sent Syntevo a while back, with various performance stats for command-line git.) Obviously if the lift is huge or the desire from the devs is not present that's understandable. The combining of the best UX/UI experience of SmartGit with radical new features is something I"m on board for. I posted this topic originally because I could not find any other git client that had this capability and it would be a super nice one to have.

Linux smartgit software#

I understand that SmartGit has the capability to use an internal git or a external git binary, and obviously the server would be required to have the git extension installed, but these are problems that have basically already been solved in your software product in regards to local.

Linux smartgit code#

The use case for this would be pulling code to a remote server without having to ssh manually into the server and type git pull (or whatever commands). From there, the software would act like it does now, but instead of executing commands on the local computer, it would execute commands on the remote server and report the output in the output window.

Linux smartgit password#

I would say the integration should just allow you to put in a remote ssh connection and a path so something like and then either a password or an ssh key. This process is largely for security reasons, however, the concept is an interesting one. If you have ever used MySQL or another database, you know some clients (SequelPro for example) have the capability to connect via SSH first then connect to the server. What I originally had in mind was not a VS code extension, but more like a connect via SSH. In that regard, I do use VS Code for coding but do not use their git extension because I think SmartGit works better for me.

It is my opinion that SmartGit has the best UI in terms of reflecting the terminology and workflow of the git system, as opposed to some of your competitors.

Surprised this is getting traction, but I guess that is how the world works.įor the record, I have been a long time SmartGit user and use the product almost daily. I am the original poster of the comment from four years ago. (I understand about the low priority, but we can dream, can't we?) This ignores when SmartGit directly accesses the file system, but perhaps that's well-capsulated and so could be easily redirected across ssh. The obvious thought is to have SmartGit reach across the network and call git on the remote machine, thus drastically cutting back on the network traffic required. I don't know SmartGit's internals, but it seems to do a lot of its intensive file access by directly calling the git tool. (Separate gripe: tens of thousands of source files, and somehow it's important to have those twelve pairs of files whose names differ only by case? Grrrrr.)

Linux smartgit windows#

Note also that I'm compiling the Linux kernel, which can only be done on a case-sensitive file system, and macOS and Windows are case-insensitive. It's also proximal to the hardware I'm developing for. I'd have to commit and check out every time I wanted to compile. Yes, I could use a local clone, but the remote machine is a monster Linux compile engine with the cross-platform development tools I need. This means that we must go back to caveman days and use command-line git to manipulate files on the remote machine. Even if sshfs is used, the latency to the server makes file sharing far too slow for the disk-access-heavy actions that git and SmartGit use. Remote machines always support ssh, but almost never file sharing.