commit 1df49831b582650d5f200bc2821f4f52811d4af8 parent 250f6c07bf3a76e9762c2b8f2979652c002f254d Author: pyratebeard <root@pyratebeard.net> Date: Mon, 10 Jun 2024 21:55:45 +0100 up_git_stream Diffstat:
| M | entry/up_git_stream.md | | | 2 | +- |
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/entry/up_git_stream.md b/entry/up_git_stream.md @@ -4,7 +4,7 @@ Instead, over the years I have grown use to running `git fetch` and `git merge` The reason for this is so that I can review the log and any changes before merging the remote code into my local repo. -I would try to remember to run `git log` after fetching the remote code, so I can review the log. Until I read about the dotted range notation and `@` construct for specifying [revisions][1] in Git. +I would try to remember to run `git log` after fetching the remote code, which by default would show the entire log history of the repo. Then I read about the dotted range notation and `@` construct for specifying [revisions][1] in Git. Using `@` on is own is equal to `HEAD`. Combine it in `git log` with `{upstream}` or `{u}` to only show commit logs for the upstream branch