I'm a SourceTree user on Mac. Just tried GitUp out for an hour. Here are the problems I have with SourceTree: * Slow as hell * No/bad keyboard shorts, and setting up custom ones is annoying and buggy * Uses tons of memory — it eventually gets up to 1 GB after running for a day or two, and my repos are not very big. My thoughts on GitUp: * Crazy fast (almost disarmingly so – I think it needs more visual confirmation w…
Thanks for trying GitUp and for the feedback! > The list of commits (Cmd+D) in the map view is useless Could you provide feedback on http://forums.gitup.co about what you are specifically trying to do or what your workflow is?
GitUp makes Git painless
101–110 of 260 posts
Re: GitUp makes Git painless
#102>>Requires Mac OS X 10.8 or later Apparently it is not the interface I have been missing... Having a Git tool not available for Linux is blasphemy
Yeah, I simply don't understand this recent tendency to launch on Mac first. Out of the big 3 (Linux, Windows, Mac), Mac is by far the worst platform to launch on because you have to buy hardware. Please can we stop it now. Just launch on Linux - everyone can access Linux no matter whether they are PC or Mac.
Yea, I'm a huge fan of the free hardware they give away when you download open source operating systems.
Re: GitUp makes Git painless
#103Earlier quoted context omitted.
You don't need to make an application closed source to have in app purchases. Look at mobaxterm [ http://mobaxterm.mobatek.net/license.html ] It is licensed under GPL version 3. It has a free version and a professional version which cost $69 per user. This does not break the GPL. You may already know this but it seems like a lot of developers think open source mean Free as in cost. [ http://www.gnu.org/philosophy/sel…
Although the GPL allows authors to charge for software, it disposes of all legal copyright protections that make such charges practical. Charging for GPL software doesn't mean anyone will pay you, it just means that everyone will get the free builds from someone else, which is even less desirable than releasing free builds since you lose control of distribution. Look at Red Hat and CentOS for case in point.
Re: GitUp makes Git painless
#104I like the name GitUp for two reasons. First, it has the meaning "get up," and second, if you say "GitUp" out loud, people would reasonably hear "GitHub," then you'd have to launch into an explanation of the differences between the two.
Re: GitUp makes Git painless
#105I realize this is a pretty broad question, but what is it about Git that people find painful ? Could be Stockholm Syndrome on my part, but I have a pretty hard time understanding why someone can't spend a week getting up to speed with a tool they intend to use for years to come.
ain't nobody got time for that
Re: GitUp makes Git painless
#106There's something really satisfying about seeing a visual representation of my git repositories, but my overall impression is that I'm not going to get any productivity gains here. If you know what you're doing, CLI is just faster. I understand that it's aimed at more novice developers, but I think for those developers it's even more important to use the command line. Developers that get into the habit of using unnec…
gr = !git \
--no-pager \
log -n 16 --graph --date-order --date=short --branches \
--pretty=\
'%C(yellow bold)%h%Creset\
%Creset %C(blue bold)%d%Creset\
%C(white bold blink)%s'
The 'gr' is short for 'graph'. You can tweak the -n to show more history. I actually have several of these, 'gr', 'grr', 'grrr', etc. to show more and more history.Re: GitUp makes Git painless
#107I realize this is a pretty broad question, but what is it about Git that people find painful ? Could be Stockholm Syndrome on my part, but I have a pretty hard time understanding why someone can't spend a week getting up to speed with a tool they intend to use for years to come.
IMO this all boils down to the Git CLI just being terrible e.g. “git add” to stage versus “git reset HEAD” to unstage. Pretty much everything is like that. And there are always edge cases so that a command works in this case but not in that one. Want to edit a commit message? "git amend". But only if the last one. Otherwise it's "git rebase -i" (even though your intent is not to do a rebase, go figure). Well, not if it's a merge actually, you'd need "git rebase -p" or something... Even if something is conceptually simple, Git CLI manages to make it complicated. And GUI tools don't help much as they just wrap the Git CLI.
Of course it does make sense if you know how Git is built internally, but that's irrelevant to getting the job done :)
Anyway, with GitUp, the idea is to have an interactive live map instead, where operations and UI actually make sense, while still being 100% compatible with Git under the hood.
Re: GitUp makes Git painless
#108It's kind of amusing to me how the pendulum has swung, and we're now producing OS X-only developer software. But then, I'm an oddball who works on Windows as my shell with the real work happening on a headless Linux box via SSH and Samba for 99% of my development.
Re: GitUp makes Git painless
#109Earlier quoted context omitted.
What is wrong for charging money for a product you spend time developing that people want to buy because it provides them value?
Nothing. And don't worry. If this turns out to be successful, the OSS community will copy this idea in no time.
Re: GitUp makes Git painless
#110For my co-founder who's just getting started with software engineering practices like version control, I recommended she use ungit (https://github.com/FredrikNoren/ungit)