|
154 | 154 | <CAKvOHKAFXQwt4D8yUCCkf_TQL79mYaJ=KAKhtpDNTvHJFuX1NA@mail.gmail.com>, |
155 | 155 | |
156 | 156 |
|
| 157 | +* Support for storing shorthands for remote URLs in "$GIT_COMMON_DIR/branches/" |
| 158 | + and "$GIT_COMMON_DIR/remotes/" has been long superseded by storing remotes in |
| 159 | + the repository configuration. |
| 160 | ++ |
| 161 | +The mechanism has originally been introduced in f170e4b39d ([PATCH] fetch/pull: |
| 162 | +short-hand notation for remote repositories., 2005-07-16) and was superseded by |
| 163 | +6687f8fea2 ([PATCH] Use .git/remote/origin, not .git/branches/origin., |
| 164 | +2005-08-20), where we switched from ".git/branches/" to ".git/remotes/". That |
| 165 | +commit already mentions an upcoming deprecation of the ".git/branches/" |
| 166 | +directory, and starting with a1d4aa7424 (Add repository-layout document., |
| 167 | +2005-09-01) we have also marked this layout as deprecated. Eventually we also |
| 168 | +started to migrate away from ".git/remotes/" in favor of config-based remotes, |
| 169 | +and we have marked the directory as legacy in 3d3d282146 (Documentation: |
| 170 | +Grammar correction, wording fixes and cleanup, 2011-08-23) |
| 171 | ++ |
| 172 | +As our documentation mentions, these directories are not to be found in modern |
| 173 | +repositories at all and most users aren't even aware of these mechanisms. They |
| 174 | +have been deprecated for almost 20 years and 14 years respectively, and I am |
| 175 | +not aware of any reason why anybody would want to use these mechanisms. |
| 176 | +Furthermore, the ".git/branches/" directory is noadays misleadingly named and |
| 177 | +may cause confusion as "branches" are almost exclusively used in the context of |
| 178 | +references. |
| 179 | ++ |
| 180 | +These features will be removed. |
| 181 | + |
157 | 182 | == Superseded features that will not be deprecated |
158 | 183 |
|
159 | 184 | Some features have gained newer replacements that aim to improve the design in |
|
0 commit comments