All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git-remote
Date: Mon, 8 Jan 2007 23:28:51 -0500	[thread overview]
Message-ID: <20070109042851.GF1686@fieldses.org> (raw)
In-Reply-To: <7vfyarokk7.fsf@assigned-by-dhcp.cox.net>

On Wed, Jan 03, 2007 at 01:40:56PM -0800, Junio C Hamano wrote:
> 	$ git add another git://git.kernel.org/pub/...
> 
> defines the default remote.another.url and remote.another.fetch
> entries just like a clone does; you can say "git fetch another"
> afterwards.

Nifty.

Would it make sense for "git add" to do the initial fetch as well?

That'd also help catch any typos in the URL early--the first time I used
this I mistyped the URL, then had to delete the configuration by hand
after I found the problem....

How about this as a man page?

--b.

Documentation: add git-remote man page

Add a preliminary man page for git-remote.

Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
---
 Documentation/git-remote.txt |   76 ++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 76 insertions(+), 0 deletions(-)

diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt
new file mode 100644
index 0000000..7d6663e
--- /dev/null
+++ b/Documentation/git-remote.txt
@@ -0,0 +1,76 @@
+git-remote(1)
+============
+
+NAME
+----
+git-remote - manage set of tracked repositories
+
+
+SYNOPSIS
+--------
+[verse]
+'git-remote'
+'git-remote' add <name> <url>
+'git-remote' show <name>
+
+DESCRIPTION
+-----------
+
+Manage the set of repositories ("remotes") whose branches you track.
+
+With no arguments, shows a list of existing remotes.
+
+In the second form, adds a remote named <name> for the repository at
+<url>.  The command `git fetch <name>` can then be used to create and
+update remote-tracking branches <name>/<branch>.
+
+In the third form, gives some information about the remote <name>.
+
+The remote configuration is achieved using the `remote.origin.url` and
+`remote.origin.fetch` configuration variables.  (See
+gitlink:git-repo-config[1]).
+
+Examples
+--------
+
+Add a new remote, fetch, and check out a branch from it:
+
+------------
+$ git remote
+origin
+$ git branch -r
+origin/master
+$ git remote add linux-nfs git://linux-nfs.org/pub/nfs-2.6.git
+$ git remote
+linux-nfs
+origin
+$ git fetch
+* refs/remotes/linux-nfs/master: storing branch 'master' ...
+  commit: bf81b46
+$ git branch -r
+origin/master
+linux-nfs/master
+$ git checkout -b nfs linux-nfs/master
+...
+------------
+
+See Also
+--------
+gitlink:git-fetch[1]
+gitlink:git-branch[1]
+gitlink:git-repo-config[1]
+
+Author
+------
+Written by Junio Hamano 
+
+
+Documentation
+--------------
+Documentation by J. Bruce Fields and the git-list <git@vger.kernel.org>.
+
+
+GIT
+---
+Part of the gitlink:git[7] suite
+
-- 
1.4.4.4.g4083

  parent reply	other threads:[~2007-01-09  4:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03 21:40 [RFC] git-remote Junio C Hamano
2007-01-03 22:05 ` Jakub Narebski
2007-01-05  3:02 ` Shawn O. Pearce
2007-01-05  3:07   ` Junio C Hamano
2007-01-05  3:17     ` Shawn O. Pearce
2007-01-05 12:59 ` Santi Béjar
2007-01-05 13:53   ` Johannes Schindelin
2007-01-05 19:53     ` Santi Béjar
2007-01-05 21:08       ` Carl Worth
2007-01-06  1:59         ` Junio C Hamano
2007-01-08 22:52           ` Carl Worth
2007-01-09  4:28 ` J. Bruce Fields [this message]
2007-01-09  5:48   ` Junio C Hamano
2007-01-09  5:50   ` Junio C Hamano
2007-01-09  9:22     ` Andreas Ericsson
2007-01-10 18:13       ` J. Bruce Fields

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=20070109042851.GF1686@fieldses.org \
    --to=bfields@fieldses.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.