@matheusbsbs / matheus-bagliano / commits / 674735836e
Fork 0

Repository cloned with 1.5.0 uses wildcard refspec

This makes fetching into such a repository using older git impossible until the remote.*.fetch lines are downgraded. Warn mildly about this.

Junio C Hamano committed Jan 15, 2007 at 14:42 UTC 674735836e1a9fe2f97b79955405f304352a65cd
1 file changed +10 -3
v1.5.0.txt
+10 -3
@@ -107,9 +107,16 @@ Updates in v1.5.0 since v1.4.4 series
107 - git-clone always uses what is known as "separate remote"
108 layout for a newly created repository with a working tree;
109 i.e. tracking branches in $GIT_DIR/refs/remotes/origin/ are
110 - used to track branches from the origin. New branches that
111 - appear on the origin side after a clone is made are also
112 - tracked automatically.
110 + used to track branches from the origin.
111 +
112 + - New branches that appear on the origin side after a clone is
113 + made are also tracked automatically. This is done with an
114 + wildcard refspec "refs/heads/*:refs/remotes/origin/*", which
115 + older git does not understand, so if you clone with 1.5.0,
116 + you would need to downgrade remote.*.fetch in the
117 + configuration file to specify each branch you are interested
118 + in individually if you plan to fetch into the repository with
119 + older versions of git (but why would you?).
120
121 - git-branch and git-show-branch know remote tracking branches.
122