diff options
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | 2015-06-22 15:27:18 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2015-06-23 21:27:37 (GMT) |
| commit | cd94c6f91ee92ffb0592696170fa84f426b839ab (patch) | |
| tree | 1e437d580bb4b5087d248d69149350ebf14ed94b /Documentation | |
| parent | 02976bf856bc47ea2bcb9423cd13b6f69ce58929 (diff) | |
| download | git-cd94c6f91ee92ffb0592696170fa84f426b839ab.zip git-cd94c6f91ee92ffb0592696170fa84f426b839ab.tar.gz git-cd94c6f91ee92ffb0592696170fa84f426b839ab.tar.bz2 | |
fsck: git receive-pack: support excluding objects from fsck'ing
The optional new config option `receive.fsck.skipList` specifies the path
to a file listing the names, i.e. SHA-1s, one per line, of objects that
are to be ignored by `git receive-pack` when `receive.fsckObjects = true`.
This is extremely handy in case of legacy repositories where it would
cause more pain to change incorrect objects than to live with them
(e.g. a duplicate 'author' line in an early commit object).
The intended use case is for server administrators to inspect objects
that are reported by `git push` as being too problematic to enter the
repository, and to add the objects' SHA-1 to a (preferably sorted) file
when the objects are legitimate, i.e. when it is determined that those
problematic objects should be allowed to enter the server.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/config.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/config.txt b/Documentation/config.txt index 1c65767..f6cbd6d 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -2222,6 +2222,14 @@ which would not pass pushing when `receive.fsckObjects = true`, allowing the host to accept repositories with certain known issues but still catch other issues. +receive.fsck.skipList:: + The path to a sorted list of object names (i.e. one SHA-1 per + line) that are known to be broken in a non-fatal way and should + be ignored. This feature is useful when an established project + should be accepted despite early commits containing errors that + can be safely ignored such as invalid committer email addresses. + Note: corrupt objects cannot be skipped with this setting. + receive.unpackLimit:: If the number of objects received in a push is below this limit then the objects will be unpacked into loose object |