git-svn: add --prefix= option to multi-init

[git.git] / Documentation / git-receive-pack.txt

diff --git a/Documentation/git-receive-pack.txt b/Documentation/git-receive-pack.txt
index fb4b76b6c2459bc8341ff879c961170b015d1054..0dfadc2a32a44ef1e026ae95c8cc5906ec4d4d5c 100644 (file)
--- a/Documentation/git-receive-pack.txt
+++ b/Documentation/git-receive-pack.txt
@@ -1,6 +1,5 @@
 git-receive-pack(1)
 ===================
 git-receive-pack(1)
 ===================

-v0.1, July 2005

 
 NAME
 ----
 
 NAME
 ----


@@ -19,8 +18,7 @@ information fed from the remote end.
 This command is usually not invoked directly by the end user.
 The UI for the protocol is on the 'git-send-pack' side, and the
 program pair is meant to be used to push updates to remote
 This command is usually not invoked directly by the end user.
 The UI for the protocol is on the 'git-send-pack' side, and the
 program pair is meant to be used to push updates to remote

-repository.  For pull operations, see 'git-fetch-pack' and
-'git-clone-pack'.
+repository.  For pull operations, see 'git-fetch-pack'.

 
 The command allows for creation and fast forwarding of sha1 refs
 (heads/tags) on the remote end (strictly speaking, it is the
 
 The command allows for creation and fast forwarding of sha1 refs
 (heads/tags) on the remote end (strictly speaking, it is the


@@ -72,6 +70,12 @@ packed and is served via a dumb transport.
        #!/bin/sh
        exec git-update-server-info
 
        #!/bin/sh
        exec git-update-server-info
 

+There are other real-world examples of using update and
+post-update hooks found in the Documentation/howto directory.
+
+git-receive-pack honours the receive.denyNonFastforwards flag, which
+tells it if updates to a ref should be denied if they are not fast-forwards.
+

 OPTIONS
 -------
 <directory>::
 OPTIONS
 -------
 <directory>::