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

[PATCH v2 3/4] Documentation: Update the NFS remote examples to use the staging repo

From
W. Trevor King <wking@tremily.us>
Date
Jun 22, 2013, 14:46 UTC
Message-ID
<d668c4fac602e8f97a7abdb36a169b5a67bc3383.1371911897.git.wking@tremily.us>
In-Reply-To
<cover.1371911897.git.wking@tremily.us>
From: "W. Trevor King" <wking@tremily.us>

linux-nfs.org seems to have restructured their repository layout since 8391c60 (git-remote.txt: fix example url, 2007-11-02), and Bruce's repo is now at git://git.linux-nfs.org/projects/bfields/linux.git. Bruce also has a more richer internal branch structure (master, everything, for-3.1, ...), so updating the existing example to use his current repo may be confusing.

To simplify, I've replaced the NFS repo with Greg's staging repo. I've also updated the output of the surrounding commands to match the output of a current run through.

Signed-off-by: W. Trevor King <wking@tremily.us>
---
 Documentation/git-remote.txt  | 25 ++++++++++++++++---------
 Documentation/user-manual.txt | 26 ++++++++++++++++----------
 2 files changed, 32 insertions(+), 19 deletions(-)
diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt
index 7a6f354..d007163 100644
--- a/Documentation/git-remote.txt
+++ b/Documentation/git-remote.txt
@@ -187,18 +187,25 @@ Examples
 $ git remote
 origin
 $ git branch -r
-origin/master
-$ git remote add linux-nfs git://linux-nfs.org/pub/linux/nfs-2.6.git
+  origin/HEAD -> origin/master
+  origin/master
+$ git remote add staging git://git.kernel.org/.../gregkh/staging.git
 $ git remote
-linux-nfs
 origin
-$ git fetch
-* refs/remotes/linux-nfs/master: storing branch 'master' ...
-  commit: bf81b46
+staging
+$ git fetch staging
+...
+From git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
+ * [new branch]      master     -> staging/master
+ * [new branch]      staging-linus -> staging/staging-linus
+ * [new branch]      staging-next -> staging/staging-next
 $ git branch -r
-origin/master
-linux-nfs/master
-$ git checkout -b nfs linux-nfs/master
+  origin/HEAD -> origin/master
+  origin/master
+  staging/master
+  staging/staging-linus
+  staging/staging-next
+$ git checkout -b staging staging/master
 ...
 ------------
 
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index e831cc2..4283d8f 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -431,19 +431,25 @@ You can also track branches from repositories other than the one you
 cloned from, using linkgit:git-remote[1]:
 
 -------------------------------------------------
-$ git remote add linux-nfs git://linux-nfs.org/pub/nfs-2.6.git
-$ git fetch linux-nfs
-* refs/remotes/linux-nfs/master: storing branch 'master' ...
-  commit: bf81b46
+$ git remote add staging git://git.kernel.org/.../gregkh/staging.git
+$ git fetch staging
+...
+From git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
+ * [new branch]      master     -> staging/master
+ * [new branch]      staging-linus -> staging/staging-linus
+ * [new branch]      staging-next -> staging/staging-next
 -------------------------------------------------
 
 New remote-tracking branches will be stored under the shorthand name
-that you gave `git remote add`, in this case `linux-nfs`:
+that you gave `git remote add`, in this case `staging`:
 
 -------------------------------------------------
 $ git branch -r
-linux-nfs/master
-origin/master
+  origin/HEAD -> origin/master
+  origin/master
+  staging/master
+  staging/staging-linus
+  staging/staging-next
 -------------------------------------------------
 
 If you run `git fetch <remote>` later, the remote-tracking branches
@@ -455,9 +461,9 @@ a new stanza:
 -------------------------------------------------
 $ cat .git/config
 ...
-[remote "linux-nfs"]
-	url = git://linux-nfs.org/pub/nfs-2.6.git
-	fetch = +refs/heads/*:refs/remotes/linux-nfs/*
+[remote "staging"]
+	url = git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
+	fetch = +refs/heads/*:refs/remotes/staging/*
 ...
 -------------------------------------------------
 
-- 
1.8.3
Previous: W. Trevor KingNext: W. Trevor King
Message 11 of 18 in “Update linux-2.6.git location and repo size”
  1. 0/2 Update linux-2.6.git location and repo sizeW. Trevor King, Jun 19, 2013
  2. 1/2 Documentation: Update 'linux-2.6.git' -> 'linux.git'W. Trevor King, Jun 19, 2013
  3. David AguilarJun 19, 2013
  4. W. Trevor KingJun 19, 2013
  5. Junio C HamanoJun 19, 2013
  6. W. Trevor KingJun 19, 2013
  7. Junio C HamanoJun 19, 2013
  8. 0/4 Update linux-2.6.git location and related examplesW. Trevor King, Jun 22, 2013
  9. 1/4 doc/clone: Remove the '--bare -l -s' exampleW. Trevor King, Jun 22, 2013
  10. 2/4 doc/clone: Pick more compelling paths for the --reference exampleW. Trevor King, Jun 22, 2013
  11. 3/4 Documentation: Update the NFS remote examples to use the staging repoW. Trevor King, Jun 22, 2013
  12. 4/4 Documentation: Update 'linux-2.6.git' -> 'linux.git'W. Trevor King, Jun 22, 2013
  13. W. Trevor KingJun 30, 2013
  14. Junio C HamanoJun 30, 2013
  15. W. Trevor KingJun 30, 2013
  16. 2/2 user-manual: Update download size for Git and the kernelW. Trevor King, Jun 19, 2013
  17. Junio C HamanoJun 19, 2013
  18. W. Trevor KingJun 22, 2013

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.