commit 0154a2e3a79acf31bbe26d3ffc26fdf72e4c2ac5 parent 1df49831b582650d5f200bc2821f4f52811d4af8 Author: pyratebeard <root@pyratebeard.net> Date: Mon, 10 Jun 2024 21:58:21 +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 @@ -1,6 +1,6 @@ Unlike most people (I imagine) I rarely, if ever, run `git pull` when refreshing my local Git repositories. -Instead, over the years I have grown use to running `git fetch` and `git merge` separately (a `pull` does both of these in one command). +Instead, over the years I have grown accustomed to running `git fetch` and `git merge` separately (a `pull` does both of these in one command). The reason for this is so that I can review the log and any changes before merging the remote code into my local repo.