Got it! For a long time now I've been asking (in a variety of ways)[1] "how do I find out what will get pushed if I `git push`". The answer seems to be $ git log origin..HEAD Notes ----- [1] Here are 2 posted here from this year: 03-08> how do I ask the question "hey, it's been a long time 03-08> since I worked in this branch, what had I changed herein?" 06-26> So that means I've committed 3 times that I don't 06-26> remember. How do I find out what those commits were?
Might not work for everyone, depending on their setup.
If you want to be 100% explicit, I think you want
git log origin/dev..HEAD
If your default remote branch is already set to dev (and it might be) then
your version will work. Mine was set to master, so I would get all the
commits we've made since the last release.
git remote set-head origin dev
will set your default branch for the origin remote to 'dev', and then
everything will work as expected. I *think* if you cloned since we switched
over to using 'dev' as our main repo, then everything will already work the
way it does for Syd.
On Sun, Dec 4, 2016 at 8:28 AM, Syd Bauman
Got it!
For a long time now I've been asking (in a variety of ways)[1] "how do I find out what will get pushed if I `git push`". The answer seems to be
$ git log origin..HEAD
Notes ----- [1] Here are 2 posted here from this year:
03-08> how do I ask the question "hey, it's been a long time 03-08> since I worked in this branch, what had I changed herein?"
06-26> So that means I've committed 3 times that I don't 06-26> remember. How do I find out what those commits were? -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
participants (2)
-
Hugh Cayless -
Syd Bauman