2005-07-14 09:08:05 +02:00
|
|
|
git-unpack-objects(1)
|
|
|
|
|
=====================
|
|
|
|
|
|
|
|
|
|
NAME
|
|
|
|
|
----
|
2006-03-09 17:24:50 +01:00
|
|
|
git-unpack-objects - Unpack objects from a packed archive
|
2005-07-14 09:08:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
2011-07-02 04:38:26 +02:00
|
|
|
[verse]
|
usage: do not insist that standard input must come from a file
The synopsys text and the usage string of subcommands that read list
of things from the standard input are often shown like this:
git gostak [--distim] < <list-of-doshes>
This is problematic in a number of ways:
* The way to use these commands is more often to feed them the
output from another command, not feed them from a file.
* Manual pages outside Git, commands that operate on the data read
from the standard input, e.g "sort", "grep", "sed", etc., are not
described with such a "< redirection-from-file" in their synopsys
text. Our doing so introduces inconsistency.
* We do not insist on where the output should go, by saying
git gostak [--distim] < <list-of-doshes> > <output>
* As it is our convention to enclose placeholders inside <braket>,
the redirection operator followed by a placeholder filename
becomes very hard to read, both in the documentation and in the
help text.
Let's clean them all up, after making sure that the documentation
clearly describes the modes that take information from the standard
input and what kind of things are expected on the input.
[jc: stole example for fmt-merge-msg from Jonathan]
Helped-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-10-16 20:27:42 +02:00
|
|
|
'git unpack-objects' [-n] [-q] [-r] [--strict]
|
2005-07-14 09:08:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
-----------
|
2006-05-05 21:05:36 +02:00
|
|
|
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
|
2015-05-17 08:56:53 +02:00
|
|
|
from the packfile. Therefore, nothing will be unpacked if you use
|
|
|
|
|
this command on a packfile that exists within the target repository.
|
2006-05-05 21:05:36 +02:00
|
|
|
|
2008-06-30 20:56:34 +02:00
|
|
|
See linkgit:git-repack[1] for options to generate
|
2006-05-05 21:05:36 +02:00
|
|
|
new packs and replace existing ones.
|
2005-07-14 09:08:05 +02:00
|
|
|
|
2005-08-12 10:45:52 +02:00
|
|
|
OPTIONS
|
|
|
|
|
-------
|
2005-11-15 00:20:01 +01:00
|
|
|
-n::
|
2007-06-06 23:23:16 +02:00
|
|
|
Dry run. Check the pack file without actually unpacking
|
|
|
|
|
the objects.
|
2005-11-15 00:20:01 +01:00
|
|
|
|
2005-08-12 10:45:52 +02:00
|
|
|
-q::
|
|
|
|
|
The command usually shows percentage progress. This
|
|
|
|
|
flag suppresses it.
|
|
|
|
|
|
2006-09-04 07:55:54 +02:00
|
|
|
-r::
|
|
|
|
|
When unpacking a corrupt packfile, the command dies at
|
|
|
|
|
the first corruption. This flag tells it to keep going
|
2006-09-13 21:59:20 +02:00
|
|
|
and make the best effort to recover as many objects as
|
2006-09-04 07:55:54 +02:00
|
|
|
possible.
|
|
|
|
|
|
2008-02-25 22:46:11 +01:00
|
|
|
--strict::
|
|
|
|
|
Don't write objects with broken content or links.
|
|
|
|
|
|
2005-07-14 09:08:05 +02:00
|
|
|
GIT
|
|
|
|
|
---
|
2008-06-06 09:07:32 +02:00
|
|
|
Part of the linkgit:git[1] suite
|