{"thread":{"id":"18024","subject":"[WARNING] Proposed future changes that are backward incompatible","startedAt":"2009-02-26T01:28:20Z","lastAt":"2009-02-26T01:28:20Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"106282","messageId":"7vy6vux9zf.fsf@gitster.siamese.dyndns.org","threadId":"18024","inReplyTo":null,"subject":"[WARNING] Proposed future changes that are backward incompatible","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-02-26T01:28:20Z","receivedAt":"2009-02-26T01:28:20Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here is a list of possible future changes to git that are backward\nincompatible that are under discussion on the git mailing list.\n\nNone of them will be in the upcoming 1.6.2 release, but some of them are\nlikely to appear in future versions.  If you think we should not introduce\nsome of the listed changes, here is a chance to voice your opinions and\nmake a convincing argument against them, so please do so.  Many people\ncomplained about the removal of many git-foo commands from user's PATH,\nwhich was done in 1.6.0 based on user input, after it happened.  You do\nnot want to see such a mess happen again.\n\nThanks.\n\n* refuse push to update the checked out branch in a non-bare repo by default\n\n  Make \"git push\" into a repository to update the branch that is checked\n  out fail by default.  You can countermand this default by setting a\n  configuration variable in the receiving repository.\n\n  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007\n\n* git-push to delete the current branch will be refused by default\n\n  Make \"git push $there :$killed\" to delete the branch that is pointed at\n  by its HEAD fail by default.  You can countermand this default by\n  setting a configuration variable in the receiving repository.\n\n  http://thread.gmane.org/gmane.comp.version-control.git/108862/focus=108936\n\n* git-send-email won't make deep threads by default\n\n  Many people said that by default when sending more than 2 patches the\n  threading git-send-email makes by default is hard to read, and they\n  prefer the default be one cover letter and each patch as a direct\n  follow-up to the cover letter.  You can countermand this by setting a\n  configuration variable.\n\n  http://article.gmane.org/gmane.comp.version-control.git/109790\n\n* make core.quotepath=false the default\n\n  By default, \"git diff\" output quotes bytes in pathnames with high bit\n  set, primarily to avoid corruption during e-mail based transfer.  This\n  however is inconvenient for human readers, and also makes some poorly\n  written user scripts that do not unquote them fail.  Change the default\n  so that they are not quoted (note that control characters such as HT are\n  always quoted).  You can countermand this by setting a configuration\n  variable.\n\n  http://thread.gmane.org/gmane.comp.version-control.git/110033\n"}]}