Jeff King <peff@xxxxxxxx> writes: > ... The principle of "remove defaults from code, and > put them into the automatically generated config file" makes sense to > me. It gives users an easy place to look to understand and change such > behavior. So even without the rest of the patches, I think this is an > improvement. If the removal of defaults do not break expectations of users of an existing repository, I'd agree. Is it the case, or the lack of default that is supposed to be there now suddenly makes the tool do unexpected things? >> Patch 4 is a reworking of my previous patch. Instead of having "git >> push" push to "all mirrors plus the magic origin branch", it will >> push to "all remotes having a push refspec". In the future, this >> will always include the origin branch because of patch 2, while >> right now the origin branch is still used if no remote has a >> push refspec (for backwards compatibility -- more discussion in the >> patch log message). Didn't we already have this discussion and don't we already have a way to define a remote that you can use to push to more than one places? >> This patch may cause incompatibilities to be warned about in >> the release notes. Luckily, these incompatibilities only affect >> users that already know their way in .git/config, because no porcelain >> command creates push refspecs. "Knowledgeable people all _can_ work around the change" does not change the fact that you are forcing existing users unnecessary change to their configurations. Why does this patch need to break existing users setups? > ... I > assume people still with ancient .git/remotes files? Are those actually > deprecated? No. Neither .git/branches. When you interact with hundreds of remote repositories, one interesting branch per each, like akpm does, the format of one-file-per-remote is far easier and simpler to work with. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
