Re:Git 2.19.0 released
by oconnor663 on Wednesday September 12, 2018 @01:29PM
(#17971044)
I alias the command `git log origin/master.. --oneline`. (You could also do `git log @{upstream}.. --oneline` if you're diligent about configuring upstream branches.) That shows you how many commits you have locally that you haven't pushed yet. I use them compulsively, almost as frequently as I use `git status`.
[ Parent
| on HN ]
I find `git show-branch --topics origin/master` (optionally adding branches) to be more useful.
Re:Git 2.19.0 released
by JoshTriplett on Wednesday September 12, 2018 @01:52PM
(#17971225)
What do you alias it to?
(Also, I tend to use just `git log origin..` rather than spelling out `origin/master`.)
> I tend to use just `git log origin..` rather than spelling out `origin/master`
Doesn't work for me:
$ git log origin..
fatal: ambiguous argument 'origin..': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
$ git log origin.. --
fatal: bad revision 'origin..'
Re:Git 2.19.0 released
by oconnor663 on Wednesday September 12, 2018 @04:18PM
(#17972791)
Maybe it will work if you do `git branch --set-upstream-to=origin/master` first? But yeah, this config issue is why I don't use @{upstream} much.
Re:Git 2.19.0 released
by oconnor663 on Wednesday September 12, 2018 @02:01PM
(#17971332)
Personally "gout", which I now realize is a disease :p
For me it's "git outgoing".