From: James Bowes <jbowes@dangerouslyinc.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: [PATCH] remote: document the 'rm' subcommand
Date: Sat, 7 Jul 2007 11:22:43 -0400 [thread overview]
Message-ID: <20070707152242.GC19782@crux.rdu.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707052338150.9789@racer.site>
Signed-off-by: James Bowes <jbowes@dangerouslyinc.com>
---
So I still think 'git remote rm' would be nice to have. Here's a bit of
documentation for it.
Documentation/git-remote.txt | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt
index 61a6022..fff40ca 100644
--- a/Documentation/git-remote.txt
+++ b/Documentation/git-remote.txt
@@ -11,6 +11,7 @@ SYNOPSIS
[verse]
'git-remote'
'git-remote' add [-t <branch>] [-m <branch>] [-f] <name> <url>
+'git-remote' rm <name>
'git-remote' show <name>
'git-remote' prune <name>
'git-remote' update [group]
@@ -46,6 +47,11 @@ With `-m <master>` option, `$GIT_DIR/remotes/<name>/HEAD` is set
up to point at remote's `<master>` branch instead of whatever
branch the `HEAD` at the remote repository actually points at.
+'rm'::
+
+Remove the remote named <name>. All remote tracking branches and
+configuration settings for the remote are removed.
+
'show'::
Gives some information about the remote <name>.
--
1.5.3.rc0.838.gdf39a-dirty
next prev parent reply other threads:[~2007-07-07 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 23:25 [PATCH] remote: add 'rm' subcommand James Bowes
2007-07-05 22:38 ` Johannes Schindelin
2007-07-07 15:22 ` James Bowes [this message]
2007-07-07 16:21 ` [PATCH] remote: document the " Johannes Schindelin
2007-07-07 20:47 ` Junio C Hamano
2007-07-14 7:41 ` Junio C Hamano
2007-09-03 10:07 ` [PATCH] remote: add " 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=20070707152242.GC19782@crux.rdu.redhat.com \
--to=jbowes@dangerouslyinc.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).