1 files changed, 5 insertions, 5 deletions
diff --git a/public/i-was-wrong-about-git-workflows.html b/public/i-was-wrong-about-git-workflows.html
index 5d74af1..af5bc37 100755
--- a/public/i-was-wrong-about-git-workflows.html
+++ b/public/i-was-wrong-about-git-workflows.html
@@ -46,11 +46,11 @@ things more streamlined but in the process of doing this, we have inadvertently
 made our lives much more complicated.<p>In conclusion, it's important to re-evaluate our workflows from time to time to
 see if they still make sense and if there are better alternatives available.
 Long-living branches can be problematic, and using tags to mark important
-milestones can simplify the development process.</div></article></main><section><hr><h2>Posts from blogs I follow around the net</h2><ul><li><a href=https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSWhyNotDirectoryToFilesystem target=_blank rel=noopener>One reason that ZFS can't turn a directory into a filesystem</a> — <a href=https://utcc.utoronto.ca/~cks/space/blog/>Chris's Wiki :: blog</a><div>One of the wishes that I and other people frequently have for ZFS
+milestones can simplify the development process.</div></article></main><section><hr><h2>Posts from blogs I follow around the net</h2><ul><li><a href=https://utcc.utoronto.ca/~cks/space/blog/linux/NFSv4ServerLockClients target=_blank rel=noopener>Finding which NFSv4 client owns a lock on a Linux NFS(v4) server</a> — <a href=https://utcc.utoronto.ca/~cks/space/blog/>Chris's Wiki :: blog</a><div>A while back I wrote an entry about finding which NFS client owns
-is the ability to take an existing directory (and everything
+a lock on a Linux NFS server, which turned
-underneath it) in a ZFS filesystem and turn it into a sub-filesystem
+out to be specific to NFS v3 (which I really should have seen coming,
-of its own. One reason for wanting this is that a number of things
+since it involved NLM and lockd). Finding the NFS v4 client that
-are set and controlled on a per-filesyst…<li><a href=http://www.landley.net/notes-2023.html#28-10-2023 target=_blank rel=noopener>October 28, 2023</a> — <a href=http://www.landley.net/notes-2023.html>Rob Landley's Blog Thing for 2023</a><div>Oh good grief, two of my least favorite licensing people, Larry Rosen
+owns a lock is, depending on your perspective, either simpl…<li><a href=http://www.landley.net/notes-2023.html#28-10-2023 target=_blank rel=noopener>October 28, 2023</a> — <a href=http://www.landley.net/notes-2023.html>Rob Landley's Blog Thing for 2023</a><div>Oh good grief, two of my least favorite licensing people, Larry Rosen
 and Bradley Kuhn, are interacting on the OSI's license-discuss
 list where the're doing
 bad computer history and insisting that a guy Larry Rosen

diff --git a/public/i-was-wrong-about-git-workflows.html b/public/i-was-wrong-about-git-workflows.html index 5d74af1..af5bc37 100755 --- a/public/i-was-wrong-about-git-workflows.html +++ b/public/i-was-wrong-about-git-workflows.html
@@ -46,11 +46,11 @@ things more streamlined but in the process of doing this, we have inadvertently
46	made our lives much more complicated.<p>In conclusion, it's important to re-evaluate our workflows from time to time to	46	made our lives much more complicated.<p>In conclusion, it's important to re-evaluate our workflows from time to time to
47	see if they still make sense and if there are better alternatives available.	47	see if they still make sense and if there are better alternatives available.
48	Long-living branches can be problematic, and using tags to mark important	48	Long-living branches can be problematic, and using tags to mark important
49	milestones can simplify the development process.</div></article></main><section><hr><h2>Posts from blogs I follow around the net</h2><ul><li><a href=https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSWhyNotDirectoryToFilesystem target=_blank rel=noopener>One reason that ZFS can't turn a directory into a filesystem</a> — <a href=https://utcc.utoronto.ca/~cks/space/blog/>Chris's Wiki :: blog</a><div>One of the wishes that I and other people frequently have for ZFS	49	milestones can simplify the development process.</div></article></main><section><hr><h2>Posts from blogs I follow around the net</h2><ul><li><a href=https://utcc.utoronto.ca/~cks/space/blog/linux/NFSv4ServerLockClients target=_blank rel=noopener>Finding which NFSv4 client owns a lock on a Linux NFS(v4) server</a> — <a href=https://utcc.utoronto.ca/~cks/space/blog/>Chris's Wiki :: blog</a><div>A while back I wrote an entry about finding which NFS client owns
50	is the ability to take an existing directory (and everything	50	a lock on a Linux NFS server, which turned
51	underneath it) in a ZFS filesystem and turn it into a sub-filesystem	51	out to be specific to NFS v3 (which I really should have seen coming,
52	of its own. One reason for wanting this is that a number of things	52	since it involved NLM and lockd). Finding the NFS v4 client that
53	are set and controlled on a per-filesyst…<li><a href=http://www.landley.net/notes-2023.html#28-10-2023 target=_blank rel=noopener>October 28, 2023</a> — <a href=http://www.landley.net/notes-2023.html>Rob Landley's Blog Thing for 2023</a><div>Oh good grief, two of my least favorite licensing people, Larry Rosen	53	owns a lock is, depending on your perspective, either simpl…<li><a href=http://www.landley.net/notes-2023.html#28-10-2023 target=_blank rel=noopener>October 28, 2023</a> — <a href=http://www.landley.net/notes-2023.html>Rob Landley's Blog Thing for 2023</a><div>Oh good grief, two of my least favorite licensing people, Larry Rosen
54	and Bradley Kuhn, are interacting on the OSI's license-discuss	54	and Bradley Kuhn, are interacting on the OSI's license-discuss
55	list where the're doing	55	list where the're doing
56	bad computer history and insisting that a guy Larry Rosen	56	bad computer history and insisting that a guy Larry Rosen