From: Andrew Ruder <andy@aeruder.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH 6/8] Update git-http-push documentation
Date: Fri, 27 Apr 2007 00:09:53 -0500 [thread overview]
Message-ID: <20070427050953.GE9798@bowser.ruder> (raw)
In-Reply-To: <20070427050550.GA9594@bowser.ruder>
Documentation/git-http-push.txt: Changing --complete to --all. Added
documentation for -d and -D to remote remote refs.
Signed-off-by: Andrew Ruder <andy@aeruder.net>
---
Documentation/git-http-push.txt | 13 +++++++++++--
1 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-http-push.txt b/Documentation/git-http-push.txt
index 4b4a461..a15cf5b 100644
--- a/Documentation/git-http-push.txt
+++ b/Documentation/git-http-push.txt
@@ -8,7 +8,7 @@ git-http-push - Push objects over HTTP/DAV to another repository
SYNOPSIS
--------
-'git-http-push' [--complete] [--force] [--verbose] <url> <ref> [<ref>...]
+'git-http-push' [--all] [--force] [--verbose] <url> <ref> [<ref>...]
DESCRIPTION
-----------
@@ -18,7 +18,7 @@ remote branch.
OPTIONS
-------
---complete::
+--all::
Do not assume that the remote repository is complete in its
current state, and verify all objects in the entire local
ref's history exist in the remote repository.
@@ -34,6 +34,15 @@ OPTIONS
Report the list of objects being walked locally and the
list of objects successfully sent to the remote repository.
+-d, -D::
+ Remove <ref> from remote repository. The specified branch
+ cannot be the remote HEAD. If -d is specified the following
+ other conditions must also be met:
+
+ - Remote HEAD must resolve to an object that exists locally
+ - Specified branch resolves to an object that exists locally
+ - Specified branch is an ancestor of the remote HEAD
+
<ref>...::
The remote refs to update.
--
1.5.2.rc0.64.g8476
next prev parent reply other threads:[~2007-04-27 5:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 5:05 [PATCH 1/8] Removing -n option from git-diff-files documentation Andrew Ruder
2007-04-27 5:09 ` [PATCH 2/8] Document additional options for git-fetch Andrew Ruder
2007-04-27 5:09 ` [PATCH 3/8] Update git-fmt-merge documentation Andrew Ruder
2007-04-27 5:09 ` [PATCH 4/8] Update git-grep documentation Andrew Ruder
2007-04-27 5:09 ` [PATCH 5/8] Update -L documentation for git-blame/git-annotate Andrew Ruder
2007-04-27 5:09 ` Andrew Ruder [this message]
2007-04-27 5:09 ` [PATCH 7/8] Update git-local-fetch documentation Andrew Ruder
2007-04-27 5:10 ` [PATCH 8/8] Update git-http-fetch documentation Andrew Ruder
2007-04-27 18:05 ` [PATCH 1/8] Removing -n option from git-diff-files documentation Petr Baudis
2007-04-29 7:05 ` Junio C Hamano
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=20070427050953.GE9798@bowser.ruder \
--to=andy@aeruder.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).