Skip to content

Commit

Permalink
doc: fix inconsistent spelling of "packfile"
Browse files Browse the repository at this point in the history
Fix remaining instances where "pack-file" is used instead of
"packfile". Some places remain where we still use "pack-file",
This is the case when we explicitly refer to a file with a
".pack" extension as opposed to a data source providing a pack
data stream.

Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
  • Loading branch information
Patrick Steinhardt authored and Junio C Hamano committed May 22, 2015
1 parent 3890dae commit bbf431c
Showing 2 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion Documentation/git-unpack-objects.txt
Original file line number Diff line number Diff line change
@@ -9,7 +9,7 @@ git-unpack-objects - Unpack objects from a packed archive
SYNOPSIS
--------
[verse]
'git unpack-objects' [-n] [-q] [-r] [--strict] < <pack-file>
'git unpack-objects' [-n] [-q] [-r] [--strict] < <packfile>


DESCRIPTION
4 changes: 2 additions & 2 deletions Documentation/technical/pack-protocol.txt
Original file line number Diff line number Diff line change
@@ -465,7 +465,7 @@ contain all the objects that the server will need to complete the new
references.

----
update-request = *shallow ( command-list | push-cert ) [pack-file]
update-request = *shallow ( command-list | push-cert ) [packfile]

shallow = PKT-LINE("shallow" SP obj-id LF)

@@ -491,7 +491,7 @@ references.
*PKT-LINE(gpg-signature-lines LF)
PKT-LINE("push-cert-end" LF)

pack-file = "PACK" 28*(OCTET)
packfile = "PACK" 28*(OCTET)
----

If the receiving end does not support delete-refs, the sending end MUST

0 comments on commit bbf431c

Please sign in to comment.