mirror of
https://github.com/git/git.git
synced 2024-11-18 06:54:55 +01:00
48bb914ed6
The point of these sections is generally to:
1. Give credit where it is due.
2. Give the reader an idea of where to ask questions or
file bug reports.
But they don't do a good job of either case. For (1), they
are out of date and incomplete. A much more accurate answer
can be gotten through shortlog or blame. For (2), the
correct contact point is generally git@vger, and even if you
wanted to cc the contact point, the out-of-date and
incomplete fields mean you're likely sending to somebody
useless.
So let's drop the fields entirely from all manpages except
git(1) itself. We already point people to the mailing list
for bug reports there, and we can update the Authors section
to give credit to the major contributors and point to
shortlog and blame for more information.
Each page has a "This is part of git" footer, so people can
follow that to the main git manpage.
48 lines
1.1 KiB
Text
48 lines
1.1 KiB
Text
git-unpack-objects(1)
|
|
=====================
|
|
|
|
NAME
|
|
----
|
|
git-unpack-objects - Unpack objects from a packed archive
|
|
|
|
|
|
SYNOPSIS
|
|
--------
|
|
'git unpack-objects' [-n] [-q] [-r] [--strict] <pack-file
|
|
|
|
|
|
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 pack-file. Therefore, nothing will be unpacked if you use
|
|
this command on a pack-file 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.
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|