3 ms·

> many people will pay for a GUI interface Then many people should purchase SmartGit client. Which supports more of the same thing (with couple more clicks, gr

> many people will pay for a GUI interface Then many people should purchase SmartGit client. Which supports more of the same thing (with couple more clicks, granted) but also has a proper tree view. Also supports linux ffs. Never working with git without it again.

onionisafruit 2y ago
I’m happy with Jetbrains conflict resolution, but the I’ve never tried SmartGit for comparison. It would take a lot for me to move because I already pay for Jetbrains IDE.
- harrall 2y ago
  I don’t think SmartGit will elevate you that much but JetBrains IDEs and SmartGit are the only two tools I pay for and have for 8 years with no regrets. I already posted in this thread but I just love these two tools and wish more people knew about both of them.
  - mvonballmo 2y ago
    +1 for SmartGit. It's much more intuitive and flexible than the JetBrains UI, which still inherits so much terminology and behavior from its "unified" view that includes being able to handle Perforce changelists. It's a bit of a mess and generally trips new users up more than it helps. If you're comfortable with it, then good for you but I've had a lot of students not being able to grok it really well.
    - onionisafruit 2y ago
      I used to feel that way about JetBrains, but I don’t notice those abstractions anymore. IDK how much of it is the iterative changes they have made over the years vs me getting used to it.
SAI_Peregrinus 2y ago
Looking at the docs I'm not sure what functionality that adds over git. It seems like just a GUI, no extra abstractions for the complicated operations. E.g. modifying older commits[1] still looks to require manually branching, resetting, making the modification, rebasing/cherry-picking from the previous branch, fixing any conflicts, and then deleting the previous branch. That's pretty shitty for a wrapper, it should just be "right click the commit, click modify, make edits, resolve any conflicts". The porcelain shouldn't expose the plumbing so much! [1] https://docs.syntevo.com/SmartGit/Latest/HowTos/Modifying-the-History https://docs.syntevo.com/SmartGit/Latest/HowTos/Modifying-th...
- gear54rus 2y ago
  > "right click the commit, click modify, make edits, resolve any conflicts" I don't know why the docs are this way, it's literally that. Maybe old version or something. This page is closer to the truth. https://docs.syntevo.com/SmartGit/Latest/Manual/GUI/Branch/Rebase-Interactive https://docs.syntevo.com/SmartGit/Latest/Manual/GUI/Branch/R... You can download it and check it out, they have trial licenses.

onionisafruit 2y ago

I’m happy with Jetbrains conflict resolution, but the I’ve never tried SmartGit for comparison. It would take a lot for me to move because I already pay for Jetbrains IDE.

harrall 2y ago
I don’t think SmartGit will elevate you that much but JetBrains IDEs and SmartGit are the only two tools I pay for and have for 8 years with no regrets. I already posted in this thread but I just love these two tools and wish more people knew about both of them.
- mvonballmo 2y ago
  +1 for SmartGit. It's much more intuitive and flexible than the JetBrains UI, which still inherits so much terminology and behavior from its "unified" view that includes being able to handle Perforce changelists. It's a bit of a mess and generally trips new users up more than it helps. If you're comfortable with it, then good for you but I've had a lot of students not being able to grok it really well.
  - onionisafruit 2y ago
    I used to feel that way about JetBrains, but I don’t notice those abstractions anymore. IDK how much of it is the iterative changes they have made over the years vs me getting used to it.

SAI_Peregrinus 2y ago

Looking at the docs I'm not sure what functionality that adds over git. It seems like just a GUI, no extra abstractions for the complicated operations. E.g. modifying older commits[1] still looks to require manually branching, resetting, making the modification, rebasing/cherry-picking from the previous branch, fixing any conflicts, and then deleting the previous branch. That's pretty shitty for a wrapper, it should just be "right click the commit, click modify, make edits, resolve any conflicts". The porcelain shouldn't expose the plumbing so much! [1] https://docs.syntevo.com/SmartGit/Latest/HowTos/Modifying-the-History https://docs.syntevo.com/SmartGit/Latest/HowTos/Modifying-th...

gear54rus 2y ago
> "right click the commit, click modify, make edits, resolve any conflicts" I don't know why the docs are this way, it's literally that. Maybe old version or something. This page is closer to the truth. https://docs.syntevo.com/SmartGit/Latest/Manual/GUI/Branch/Rebase-Interactive https://docs.syntevo.com/SmartGit/Latest/Manual/GUI/Branch/R... You can download it and check it out, they have trial licenses.