4 ms·

Or use sourcetree

• golergka 9y ago
  You can't run sourcetree output through grep, sed and xargs though.
  • taeric 9y ago
    Curious, why would you run log through those? It already has flags to support getting birth the messages and the diffs. Granted, familiarity and reflex are decent reasons.
• ozim 9y ago
  Sourcetree is awful and slow. There is git gui by default, which is not perfect but IMO better that cli. I actually use Git Extensions for years now and could not find anything better.
  • pwneduser 9y ago
    Which Git GUI present by default do you find better than CLI? gitk? Or do you have something else in mind?
    • ozim 9y ago
      This one where you just type in 'git gui' and it pops up. https://git-scm.com/docs/git-gui https://git-scm.com/docs/git-gui
      • majewsky 9y ago
        `git gui` is not a commit tree browser though. It's used for making commits.
        • ozim 9y ago
          Menu -> Repository -> Visualize You can visualize current branch or all branches. It also has search, diffs and quite some options.
    • majewsky 9y ago
      Not present by default, but I like QGit for history browsing: http://libre.tibirna.org/projects/qgit/wiki/QGit http://libre.tibirna.org/projects/qgit/wiki/QGit
• zingmars 9y ago
  I used to love sourcetree, but after the redesign the whole thing became so slow I just went back to using CLI tools. Maybe it's for the better, as I can be way more flexible this way.
  • kabes 9y ago
    Atlassian seems to be really good at redesigns that make things slow. Jira anybody?
    • imglorp 9y ago
      Doubly slow if you count hamburger menus. First you load mountains of code and assets. Then you have to remember which collapsed menu is hiding your target, then you go there and look around and hit it, then wait another 15s to load the next pile of crap. Can't they at least use the real estate if you have it, instead of always hiding? I'm tired of it. None of their thrash is benefiting me.