summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAki <please@ignore.pl>2022-01-26 19:22:56 +0100
committerAki <please@ignore.pl>2022-01-26 19:22:56 +0100
commit2f7bee19ad1c8a26da5328c45667675838853b40 (patch)
tree853bad7a20dd03f5ba113339c1e506e9736fa5d3
parent75e73abc9c784f5f1aa8c4ca7c282804800360a6 (diff)
downloadignore.pl-2f7bee19ad1c8a26da5328c45667675838853b40.zip
ignore.pl-2f7bee19ad1c8a26da5328c45667675838853b40.tar.gz
ignore.pl-2f7bee19ad1c8a26da5328c45667675838853b40.tar.bz2
Bumped last modified date of posix archival guide because I forgot previously
-rw-r--r--how_to_archive_with_posix_tar_cpio_and_pax.html2
1 files changed, 1 insertions, 1 deletions
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 09d1512..eac56f2 100644
--- a/how_to_archive_with_posix_tar_cpio_and_pax.html
+++ b/how_to_archive_with_posix_tar_cpio_and_pax.html
@@ -13,7 +13,7 @@
<article>
<h1>How to Archive With POSIX tar, cpio and pax</h1>
-<p class="subtitle">Published on 2020-07-22 22:30:00+02:00, last modified on 2021-08-11 21:35:00+02:00
+<p class="subtitle">Published on 2020-07-22 22:30:00+02:00, last modified on 2022-01-26 19:10:00+01:00
<p>The usual answer to archive anything is <a href="https://www.gnu.org/software/tar/">tar</a>. As you may see I
intentionally linked to the GNU Tar. If you are a *BSD user then you use some other implementation. Both of them follow
and extend POSIX'es standard for tar utility. Or so you would think.