From 1e7bce2627da17afc38efb8f71c9510142bcac73 Mon Sep 17 00:00:00 2001
From: airman5573 <68623798+airman5573@users.noreply.github.com>
Date: Tue, 23 Aug 2022 01:16:00 +0900
Subject: [PATCH] Update persistent-caching.md

Changing the branch does not affect the timestamp
---
 guides/persistent-caching.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guides/persistent-caching.md b/guides/persistent-caching.md
index caa055f..892936a 100644
--- a/guides/persistent-caching.md
+++ b/guides/persistent-caching.md
@@ -157,7 +157,7 @@ For different use cases there are different types of snapshots:
 
 Timestamping is very fast to capture and compare as it only needs a meta data read from filesystem. Contenthashing is slow compared to that, because it need to read the file content from filesystem. But timestamping might invalidate the cache even when the file content is the same, but only the timestamp changed. This can happen because of multiple factors:
 
-* git operations always update the timestamp. e. g. fresh clone, changing branches
+* git operations always update the timestamp. e. g. fresh clone
 * save without changes
 
 So the question is: Do you expect timestamp changes, while content stays equal? And is the extra performance cost worth it?