b0e908977e
The intent of the commit 'fetch & clone: do not output progress when not on a tty' was to make fetching and cloning less chatty when output was not redirected (such as in a cron job). However, there was a serious thinko in that commit. It assumed that the client _and_ the server got this update at the same time. But this is obviously not the case, and therefore upload-pack died on seeing the option "--no-progress". This patch fixes that issue by making it a protocol option. So, until your server is updated, you still see the progress, but once the server has this patch, it will be quiet. A minor issue was also fixed: when cloning, the checkout did not heed no_progress. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <junkio@cox.net>
47 lines
943 B
Plaintext
47 lines
943 B
Plaintext
git-upload-pack(1)
|
|
==================
|
|
|
|
NAME
|
|
----
|
|
git-upload-pack - Send objects packed back to git-fetch-pack
|
|
|
|
|
|
SYNOPSIS
|
|
--------
|
|
'git-upload-pack' [--strict] [--timeout=<n>] <directory>
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
Invoked by 'git-fetch-pack', learns what
|
|
objects the other side is missing, and sends them after packing.
|
|
|
|
This command is usually not invoked directly by the end user.
|
|
The UI for the protocol is on the 'git-fetch-pack' side, and the
|
|
program pair is meant to be used to pull updates from a remote
|
|
repository. For push operations, see 'git-send-pack'.
|
|
|
|
|
|
OPTIONS
|
|
-------
|
|
|
|
\--strict::
|
|
Do not try <directory>/.git/ if <directory> is no git directory.
|
|
|
|
\--timeout=<n>::
|
|
Interrupt transfer after <n> seconds of inactivity.
|
|
|
|
<directory>::
|
|
The repository to sync from.
|
|
|
|
Author
|
|
------
|
|
Written by Linus Torvalds <torvalds@osdl.org>
|
|
|
|
Documentation
|
|
--------------
|
|
Documentation by Junio C Hamano.
|
|
|
|
GIT
|
|
---
|
|
Part of the gitlink:git[7] suite
|