BreakingChanges: clarify branches/ and remotes/
As we have created an empty .git/branches/ hierarchy until fairly recently, these directories may be found in modern repositories, but it is highly unlikely that they are being used. Reported-by: Jakub Wilk <jwilk@jwilk.net> Acked-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Feb 25, 2025 at 15:45 UTC
887758c998c31a7f461c808cb3931318f4e5ea3f
1 file changed
+2
-2
Documentation/BreakingChanges.txt
+2
-2
@@ -169,8 +169,8 @@ 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
172
+As our documentation mentions, these directories are unlikely to be used in
173
+modern repositories and most users aren't even aware of these mechanisms. They
174
have been deprecated for almost 20 years and 14 years respectively, and we are
175
not aware of any active users that have complained about this deprecation.
176
Furthermore, the ".git/branches/" directory is nowadays misleadingly named and