aboutsummaryrefslogtreecommitdiff
path: root/Documentation/git-unpack-objects.txt
diff options
context:
space:
mode:
authorbrian m. carlson <sandals@crustytoothpaste.net>2025-01-20 01:56:02 +0000
committerJunio C Hamano <gitster@pobox.com>2025-01-21 12:56:06 -0800
commit1f010d6bdf756129db13d1367c888aa4153f6d87 (patch)
tree715708841b4980198157a60e72028e25a0059177 /Documentation/git-unpack-objects.txt
parented4cf6e8e29bebb9324ba1a400a6c07513f2d642 (diff)
downloadgit-1f010d6bdf756129db13d1367c888aa4153f6d87.tar.xz
doc: use .adoc extension for AsciiDoc files
We presently use the ".txt" extension for our AsciiDoc files. While not wrong, most editors do not associate this extension with AsciiDoc, meaning that contributors don't get automatic editor functionality that could be useful, such as syntax highlighting and prose linting. It is much more common to use the ".adoc" extension for AsciiDoc files, since this helps editors automatically detect files and also allows various forges to provide rich (HTML-like) rendering. Let's do that here, renaming all of the files and updating the includes where relevant. Adjust the various build scripts and makefiles to use the new extension as well. Note that this should not result in any user-visible changes to the documentation. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-unpack-objects.txt')
-rw-r--r--Documentation/git-unpack-objects.txt52
1 files changed, 0 insertions, 52 deletions
diff --git a/Documentation/git-unpack-objects.txt b/Documentation/git-unpack-objects.txt
deleted file mode 100644
index b3de50d710..0000000000
--- a/Documentation/git-unpack-objects.txt
+++ /dev/null
@@ -1,52 +0,0 @@
-git-unpack-objects(1)
-=====================
-
-NAME
-----
-git-unpack-objects - Unpack objects from a packed archive
-
-
-SYNOPSIS
---------
-[verse]
-'git unpack-objects' [-n] [-q] [-r] [--strict]
-
-
-DESCRIPTION
------------
-Read a packed archive (.pack) from the standard input, expanding
-the objects contained within and writing them into the repository in
-"loose" (one object per file) format.
-
-Objects that already exist in the repository will *not* be unpacked
-from the packfile. Therefore, nothing will be unpacked if you use
-this command on a packfile that exists within the target repository.
-
-See linkgit:git-repack[1] for options to generate
-new packs and replace existing ones.
-
-OPTIONS
--------
--n::
- Dry run. Check the pack file without actually unpacking
- the objects.
-
--q::
- The command usually shows percentage progress. This
- flag suppresses it.
-
--r::
- When unpacking a corrupt packfile, the command dies at
- the first corruption. This flag tells it to keep going
- and make the best effort to recover as many objects as
- possible.
-
---strict::
- Don't write objects with broken content or links.
-
---max-input-size=<size>::
- Die, if the pack is larger than <size>.
-
-GIT
----
-Part of the linkgit:git[1] suite