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
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
the send-pack end, it is updating the remote. Confused?)
There are other real-world examples of using update and
post-update hooks found in the Documentation/howto directory.
the send-pack end, it is updating the remote. Confused?)
There are other real-world examples of using update and
post-update hooks found in the Documentation/howto directory.
if expr "$oval" : '0*$' >/dev/null
then
echo "Created a new ref, with the following commits:"
if expr "$oval" : '0*$' >/dev/null
then
echo "Created a new ref, with the following commits:"
Note that it is possible for refname to not have sha1-new when this
hook runs. This can easily occur if another user modifies the ref
Note that it is possible for refname to not have sha1-new when this
hook runs. This can easily occur if another user modifies the ref
to evaluate it. It is recommended that hooks rely on sha1-new
rather than the current value of refname.
to evaluate it. It is recommended that hooks rely on sha1-new
rather than the current value of refname.
This can be used to implement any repository wide cleanup tasks.
The exit code from this hook invocation is ignored; the only thing
This can be used to implement any repository wide cleanup tasks.
The exit code from this hook invocation is ignored; the only thing