git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] git-remote

From
JFJ. Bruce Fields <bfields@fieldses.org>
Date
Jan 9, 2007, 04:28 UTC
Message-ID
<20070109042851.GF1686@fieldses.org>
In-Reply-To
<7vfyarokk7.fsf@assigned-by-dhcp.cox.net>
On Wed, Jan 03, 2007 at 01:40:56PM -0800, Junio C Hamano wrote:
Show 5 quoted lines
> 	$ 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
Previous: Carl WorthNext: Junio C Hamano
Message 12 of 16 in “[RFC] git-remote”
  1. Junio C HamanoJan 3, 2007
  2. Jakub NarebskiJan 3, 2007
  3. Shawn O. PearceJan 5, 2007
  4. Junio C HamanoJan 5, 2007
  5. Shawn O. PearceJan 5, 2007
  6. Santi BéjarJan 5, 2007
  7. Johannes SchindelinJan 5, 2007
  8. Santi BéjarJan 5, 2007
  9. Carl WorthJan 5, 2007
  10. Junio C HamanoJan 6, 2007
  11. Carl WorthJan 8, 2007
  12. J. Bruce FieldsJan 9, 2007
  13. Junio C HamanoJan 9, 2007
  14. Junio C HamanoJan 9, 2007
  15. Andreas EricssonJan 9, 2007
  16. J. Bruce FieldsJan 10, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.