I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
I will look at using --all. I usually use the branch references as below. and the order doesn't matter and more branch names could be added.
git log master my-feat
It doesn't matter which one is latest, they will both show. This is useful if I am on my-feat and it is behind master and want to see commits on master and the feat.
That also works with two feat branch names. Or say master 1.2.0 for comparing tags. Especially if I accidentally tagged a feature branch so the tag doesn't show up on master.
If your master is behind the remote and you have you git fetch then you can also compare local master with remote
git log master origin/master
Note you use online instead of oneline in the first block so needs to be fixed.
I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
Thanks for sharing.
I will look at using --all. I usually use the branch references as below. and the order doesn't matter and more branch names could be added.
It doesn't matter which one is latest, they will both show. This is useful if I am on my-feat and it is behind master and want to see commits on master and the feat.
That also works with two feat branch names. Or say
master 1.2.0
for comparing tags. Especially if I accidentally tagged a feature branch so the tag doesn't show up on master.If your master is behind the remote and you have you git fetch then you can also compare local master with remote
Note you use online instead of oneline in the first block so needs to be fixed.
If you want to be more precise you can use relative references
Start the log as if we were 5 commits behind.
And you can check it out or reset.
And reference future commits when you go back like that.