git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: git@vger.kernel.org
Cc: Patrick Steinhardt <ps@pks.im>
Subject: [PATCH 3/3] pack-protocol.txt: fix insconsistent spelling of "packfile"
Date: Sun, 17 May 2015 08:56:54 +0200	[thread overview]
Message-ID: <1431845814-2541-3-git-send-email-ps@pks.im> (raw)
In-Reply-To: <1431845814-2541-1-git-send-email-ps@pks.im>

Signed-off-by: Patrick Steinhardt <ps@pks.im>
---
 Documentation/technical/pack-protocol.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/technical/pack-protocol.txt b/Documentation/technical/pack-protocol.txt
index 462e206..812d857 100644
--- a/Documentation/technical/pack-protocol.txt
+++ b/Documentation/technical/pack-protocol.txt
@@ -502,11 +502,11 @@ MUST NOT send a push-cert command.  When a push-cert command is
 sent, command-list MUST NOT be sent; the commands recorded in the
 push certificate is used instead.
 
-The pack-file MUST NOT be sent if the only command used is 'delete'.
+The packfile MUST NOT be sent if the only command used is 'delete'.
 
-A pack-file MUST be sent if either create or update command is used,
+A packfile MUST be sent if either create or update command is used,
 even if the server already has all the necessary objects.  In this
-case the client MUST send an empty pack-file.   The only time this
+case the client MUST send an empty packfile.   The only time this
 is likely to happen is if the client is creating
 a new branch or a tag that points to an existing obj-id.
 
-- 
2.4.0

  parent reply	other threads:[~2015-05-17  6:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-17  6:56 [PATCH 1/3] git-verify-pack.txt: fix inconsistent spelling of "packfile" Patrick Steinhardt
2015-05-17  6:56 ` [PATCH 2/3] git-unpack-objects.txt: " Patrick Steinhardt
2015-05-17  6:56 ` Patrick Steinhardt [this message]
2015-05-19 19:34 ` [PATCH 1/3] git-verify-pack.txt: " Junio C Hamano
2015-05-19 22:24   ` Jeff King
2015-05-20 19:22     ` Junio C Hamano
2015-05-20 19:45       ` Junio C Hamano
2015-05-20 19:49         ` Jeff King
2015-05-20 22:37           ` Junio C Hamano
2015-05-21  2:04             ` Jeff King
2015-05-21  4:54               ` Junio C Hamano
2015-05-21  7:27                 ` [PATCH] doc: " Patrick Steinhardt
2015-05-21 16:37                   ` Junio C Hamano
2015-05-22  6:10                     ` Patrick Steinhardt
2015-05-22  6:22                   ` [PATCH v2] " Patrick Steinhardt
2015-05-22 16:00                     ` Junio C Hamano
2015-05-20  5:13   ` [PATCH 1/3] git-verify-pack.txt: " Patrick Steinhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1431845814-2541-3-git-send-email-ps@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).