From 72aa4bc1292a51f47fbcb8eaf5a2fd1097eee115 Mon Sep 17 00:00:00 2001 From: Martin Ashby Date: Sun, 25 Sep 2022 21:13:48 +0100 Subject: Add post about returning to git from fossil. Commit .hugo_build.lock file, it gets generated a lot for some reason. --- .hugo_build.lock | 0 content/posts/2022-09-25-back-to-git.md | 11 +++++++++++ 2 files changed, 11 insertions(+) create mode 100644 .hugo_build.lock create mode 100644 content/posts/2022-09-25-back-to-git.md diff --git a/.hugo_build.lock b/.hugo_build.lock new file mode 100644 index 0000000..e69de29 diff --git a/content/posts/2022-09-25-back-to-git.md b/content/posts/2022-09-25-back-to-git.md new file mode 100644 index 0000000..b55c97c --- /dev/null +++ b/content/posts/2022-09-25-back-to-git.md @@ -0,0 +1,11 @@ +--- +title: "Back to Git" +date: 2022-09-25T21:09:31+01:00 +draft: false +--- + +I moved back to git from fossil SCM, after [previously](posts/2022-03-27-fossil/) migrating the other way. + +I use git for work and so couldn't forget how to use git and go all-in on fossil, and remembering two sets of commands proved somewhat painful and I wasn't seeing the benefit of built-in issue tracking or anything like that. Now I run [gitea](https://gitea.io/) git server instead. + +Weirdly I don't have too much trouble remembering two programming languages, but I think that's slightly different somehow. -- cgit v1.2.3-ZIG