Fixed misleading tar u description

last-modified-on not updated to not dilute logs

2 files changed, 3 insertions, 3 deletions

diff --git a/atom.xml.sh b/atom.xml.sh
index 5eb2e36..d2f2491 100755
--- a/atom.xml.sh
+++ b/atom.xml.sh
@@ -14,7 +14,7 @@ dates () {
 	if [ -z "$published" ]; then
 		published=$(git rev-list --no-commit-header --pretty=%aI HEAD -- "$1" | tail -n1)
 	fi
-	local modified=$(git rev-list --after="2024-01-10 02:00+01:00" -1 --no-commit-header --pretty=%aI HEAD -- "$1")
+	local modified=$(git rev-list --after="2024-01-23 02:00+01:00" -1 --no-commit-header --pretty=%aI HEAD -- "$1")
 	[ -z "$modified" ] && modified=$(meta "last-modified-on" "$1")
 	[ -z "$modified" ] && modified=$published
 	echo "<updated>$modified</updated>"
diff --git a/how_to_archive_with_posix_tar_cpio_and_pax.html b/how_to_archive_with_posix_tar_cpio_and_pax.html
index ead23c7..ed88187 100644
--- a/how_to_archive_with_posix_tar_cpio_and_pax.html
+++ b/how_to_archive_with_posix_tar_cpio_and_pax.html
@@ -78,8 +78,8 @@ $ tar xf ../archive.tar a_file
 standard input or written to standard output depending on the operation. Good chunk of implementations assumes this as a
 default behaviour if no archive file is provided at all.
 <p>That's pretty much it about tar. The are two more functions: <code>r</code> that adds new file to existing archive,
-and <code>u</code> that first tries to update the file in archive if it exists and if it doesn't then it adds it. Note,
-that the usual compression options are not available in POSIX, they are an extension.
+and <code>u</code> that first checks if the the file exists in the archive and if it is older and only then appends the
+new revision at the end. Note, that the usual compression options are not available in POSIX, they are an extension.
 
 <h2>How To Archive With POSIX cpio utility</h2>
 <p>Heading off from the usual routes we encounter cpio. It's a more frequent sight than pax, but it still is quite niche