{"thread":{"id":"34352","subject":"What's cooking in git.git (Jul 2013, #02; Fri, 5)","startedAt":"2013-07-05T09:09:11Z","lastAt":"2013-07-07T04:00:28Z","messageCount":3,"participants":["Junio C Hamano","Jonathan Nieder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"222617","messageId":"7v4nc98jbc.fsf@alter.siamese.dyndns.org","threadId":"34352","inReplyTo":null,"subject":"What's cooking in git.git (Jul 2013, #02; Fri, 5)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-07-05T09:09:11Z","receivedAt":"2013-07-05T09:09:11Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here are the topics that have been cooking.  Commits prefixed with\n'-' are only in 'pu' (proposed updates) while commits prefixed with\n'+' are in 'next'.\n\nWe are in the middle of 5th week now in the 11-week releace cycle\nfor 1.8.4 (http://tinyurl.com/gitCal), and quite a few topics have\ngraduated to 'master'.  I'd expect the rest of the week to be slow.\n\nPlease help ensure the quality of the upcoming release by testing\nthe tip of 'master' (and if you are so inclined, 'next') early.\n\nYou can find the changes described here in the integration branches\nof the repositories listed at\n\n    http://git-blame.blogspot.com/p/git-public-repositories.html\n\n--------------------------------------------------\n[Graduated to \"master\"]\n\n* tr/test-v-and-v-subtest-only (2013-06-29) 9 commits\n  (merged to 'next' on 2013-06-30 at 1c5fac1)\n + perf-lib: fix start/stop of perf tests\n  (merged to 'next' on 2013-06-26 at 8ff4d84)\n + test-lib: support running tests under valgrind in parallel\n + test-lib: allow prefixing a custom string before \"ok N\" etc.\n + test-lib: valgrind for only tests matching a pattern\n + test-lib: verbose mode for only tests matching a pattern\n + test-lib: self-test that --verbose works\n + test-lib: rearrange start/end of test_expect_* and test_skip\n + test-lib: refactor $GIT_SKIP_TESTS matching\n + test-lib: enable MALLOC_* for the actual tests\n\n Allows N instances of tests run in parallel, each running 1/N parts\n of the test suite under Valgrind, to speed things up.\n\n--------------------------------------------------\n[New Topics]\n\n* jc/t1512-fix (2013-07-01) 2 commits\n - get_short_sha1(): correctly disambiguate type-limited abbreviation\n - t1512: correct leftover constants from earlier edition\n\n A test that should have failed but didn't revealed a bug that needs\n to be corrected.\n\n Will merge to 'next'.\n\n\n* jk/fetch-pack-many-refs (2013-07-02) 3 commits\n - fetch-pack: avoid quadratic behavior in rev_list_push\n - commit.c: make compare_commits_by_commit_date global\n - fetch-pack: avoid quadratic list insertion in mark_complete\n\n Fetching between repositories with many refs employed O(n^2)\n algorithm to match up the common objects, which has been corrected.\n\n Will merge to 'next'.\n\n\n* jk/format-patch-from (2013-07-03) 2 commits\n - teach format-patch to place other authors into in-body \"From\"\n - pretty.c: drop const-ness from pretty_print_context\n\n \"git format-patch\" learned \"--from[=whom]\" option, which sets the\n \"From: \" header to the specified person (or the person who runs the\n command, if \"=whom\" part is missing) and move the original author\n information to an in-body From: header as necessary.\n\n Will merge to 'next'.\n\n\n* ms/remote-tracking-branches-in-doc (2013-07-03) 1 commit\n - Change \"remote tracking\" to \"remote-tracking\"\n\n Will merge to 'next'.\n\n\n* tf/gitweb-extra-breadcrumbs (2013-07-04) 1 commit\n - gitweb: allow extra breadcrumbs to prefix the trail\n\n An Gitweb installation that is a part of larger site can optionally\n show extra links that point at the levels higher than the Gitweb\n pages itself in the link hierarchy of pages.\n\n Will merge to 'next'.\n\n\n* bc/commit-invalid-utf8 (2013-07-04) 2 commits\n - commit: reject overlong UTF-8 sequences\n - commit: reject invalid UTF-8 codepoints\n\n Will merge to 'next'.\n\n\n* bc/send-email-use-port-as-separate-param (2013-07-04) 1 commit\n - send-email: provide port separately from hostname\n\n Will merge to 'next'.\n\n\n* ml/cygwin-does-not-have-fifo (2013-07-05) 1 commit\n - test-lib.sh - cygwin does not have usable FIFOs\n\n Will merge to 'next'.\n\n--------------------------------------------------\n[Stalled]\n\n* rj/read-default-config-in-show-ref-pack-refs (2013-06-17) 3 commits\n - ### DONTMERGE: needs better explanation on what config they need\n - pack-refs.c: Add missing call to git_config()\n - show-ref.c: Add missing call to git_config()\n\n The changes themselves are probably good, but it is unclear what\n basic setting needs to be read for which exact operation.\n\n Waiting for clarification.\n $gmane/228294\n\n\n* hv/config-from-blob (2013-05-12) 5 commits\n - do not die when error in config parsing of buf occurs\n - teach config --blob option to parse config from database\n - config: make parsing stack struct independent from actual data source\n - config: drop cf validity check in get_next_char()\n - config: factor out config file stack management\n\n Waiting for a reroll.\n $gmane/223964\n\n\n* jh/shorten-refname (2013-05-07) 4 commits\n - t1514: refname shortening is done after dereferencing symbolic refs\n - shorten_unambiguous_ref(): Fix shortening refs/remotes/origin/HEAD to origin\n - t1514: Demonstrate failure to correctly shorten \"refs/remotes/origin/HEAD\"\n - t1514: Add tests of shortening refnames in strict/loose mode\n\n When remotes/origin/HEAD is not a symbolic ref, \"rev-parse\n --abbrev-ref remotes/origin/HEAD\" ought to show \"origin\", not\n \"origin/HEAD\", which is fixed with this series (if it is a symbolic\n ref that points at remotes/origin/something, then it should show\n \"origin/something\" and it already does).\n\n Expecting a reroll, as an early part of a larger series.\n $gmane/225137\n\n\n* jl/submodule-mv (2013-04-23) 5 commits\n - submodule.c: duplicate real_path's return value\n - rm: delete .gitmodules entry of submodules removed from the work tree\n - Teach mv to update the path entry in .gitmodules for moved submodules\n - Teach mv to move submodules using a gitfile\n - Teach mv to move submodules together with their work trees\n\n \"git mv A B\" when moving a submodule A does \"the right thing\",\n inclusing relocating its working tree and adjusting the paths in\n the .gitmodules file.\n\n Waiting for a reroll.\n $gmane/226294\n\n\n* jk/list-objects-sans-blobs (2013-06-06) 4 commits\n . archive: ignore blob objects when checking reachability\n . list-objects: optimize \"revs->blob_objects = 0\" case\n . upload-archive: restrict remote objects with reachability check\n . clear parsed flag when we free tree buffers\n\n Attempt to allow \"archive --remote=$there $arbitrary_sha1\" while\n keeping the reachability safety.\n\n Seems to break some tests in a trivial and obvious way.\n\n\n* mg/more-textconv (2013-05-10) 7 commits\n - grep: honor --textconv for the case rev:path\n - grep: allow to use textconv filters\n - t7008: demonstrate behavior of grep with textconv\n - cat-file: do not die on --textconv without textconv filters\n - show: honor --textconv for blobs\n - diff_opt: track whether flags have been set explicitly\n - t4030: demonstrate behavior of show with textconv\n\n Make \"git grep\" and \"git show\" pay attention to --textconv when\n dealing with blob objects.\n\n I thought this was pretty well designed and executed, but it seems\n there are some doubts on the list; kicked back to 'pu'.\n\n\n* mh/multimail (2013-04-21) 1 commit\n - git-multimail: a replacement for post-receive-email\n\n Waiting for the initial history to pull from.\n $gmane/223564\n\n\n* jc/format-patch (2013-04-22) 2 commits\n - format-patch: --inline-single\n - format-patch: rename \"no_inline\" field\n\n A new option to send a single patch to the standard output to be\n appended at the bottom of a message.  I personally have no need for\n this, but it was easy enough to cobble together.  Tests, docs and\n stripping out more MIMEy stuff are left as exercises to interested\n parties.\n\n Not ready for inclusion.\n\n Will discard unless we hear from anybody who is interested in\n tying its loose ends.\n\n\n* jk/gitweb-utf8 (2013-04-08) 4 commits\n - gitweb: Fix broken blob action parameters on blob/commitdiff pages\n - gitweb: Don't append ';js=(0|1)' to external links\n - gitweb: Make feed title valid utf8\n - gitweb: Fix utf8 encoding for blob_plain, blobdiff_plain, commitdiff_plain, and patch\n\n Various fixes to gitweb.\n\n Drew Northup volunteered to take a look into this.\n $gmane/226216\n\n\n* jc/show-branch (2013-06-07) 5 commits\n - show-branch: use commit slab to represent bitflags of arbitrary width\n - show-branch.c: remove \"all_mask\"\n - show-branch.c: abstract out \"flags\" operation\n - show-branch.c: lift all_mask/all_revs to a global static\n - show-branch.c: update comment style\n\n Waiting for the final step to lift the hard-limit before sending it out.\n\n--------------------------------------------------\n[Cooking]\n\n* pb/stash-refuse-to-kill (2013-07-01) 2 commits\n  (merged to 'next' on 2013-07-05 at 78ecc59)\n + git stash: avoid data loss when \"git stash save\" kills a directory\n + treat_directory(): do not declare submodules to be untracked\n\n \"git stash save\" is not just about \"saving\" the local changes, but\n also is to restore the working tree state to that of HEAD. If you\n changed a non-directory into a directory in the local change, you\n may have untracked files in that directory, which have to be killed\n while doing so, unless you run it with --include-untracked.  Teach\n the command to detect and error out before spreading the damage.\n\n This needed a small fix to \"ls-files --killed\".\n\n Will merge to 'next'.\n\n\n* es/contacts (2013-07-03) 3 commits\n - contrib: contacts: interpret committish akin to format-patch\n - contrib: contacts: add ability to parse from committish\n - contrib: add git-contacts helper\n\n A helper to read from a set of format-patch output files or a range\n of commits and find those who may have insights to the code that\n the changes touch by running a series of \"git blame\" commands.\n\n Still needs to add mailmap support and other niceties but the\n basics already look sound, and the enhancements can be done\n in-tree. Assuming that \"git contact\" is something we may want to\n have as a member of the official set of commands someday, that is.\n\n Will merge to 'next'.\n\n\n* jk/bash-completion (2013-06-30) 2 commits\n  (merged to 'next' on 2013-07-01 at 6daca44)\n + completion: learn about --man-path\n + completion: handle unstuck form of base git options\n\n Will merge to 'master'.\n\n\n* cp/submodule-custom-update (2013-07-03) 1 commit\n - submodule update: allow custom command to update submodule working tree\n\n In addition to the choice from \"rebase, merge, or checkout-detach\",\n allow a custom command to be used in \"submodule update\" to update\n the working tree of submodules.\n\n Will merge to 'next'.\n\n\n* mv/merge-ff-tristate (2013-07-02) 1 commit\n - merge: handle --ff/--no-ff/--ff-only as a tri-state option\n\n The configuration variable \"merge.ff\" was cleary a tri-state to\n choose one from \"favor fast-forward when possible\", \"always create\n a merge even when the history could fast-forward\" and \"do not\n create any merge, only update when the history fast-forwards\", but\n the command line parser did not implement the usual convention of\n \"last one wins, and command line overrides the configuration\"\n correctly.\n\n Will merge to 'next'.\n\n\n* rr/rebase-reflog-message-reword (2013-06-23) 2 commits\n - rebase -i: use a better reflog message\n - rebase: use a better reflog message\n (this branch uses rr/rebase-checkout-reflog.)\n\n \"git rebase [-i]\" used to leave just \"rebase\" as its reflog message\n for some operations. This rewords them to be more informative.\n\n Will merge to 'next'.\n\n\n* bp/mediawiki-preview (2013-07-04) 7 commits\n - git-remote-mediawiki: Add preview subcommand into git mw\n - git-remote-mediawiki: Adding git-mw command\n - git-remote-mediawiki: Factoring code between git-remote-mediawiki and Git::Mediawiki\n - git-remote-mediawiki: Update tests to run with the new bin-wrapper\n - git-remote-mediawiki: New git bin-wrapper for developement\n - wrap-for-bin: Make bin-wrappers chainable\n - git-remote-mediawiki: Introduction of Git::Mediawiki.pm\n\n Looks like this is in a fairly good shape?\n\n\n* fg/submodule-clone-depth (2013-07-03) 1 commit\n - Add --depth to submodule update/add\n\n Allow shallow-cloning of submodules with \"git submodule update\".\n\n Will merge to 'next'.\n\n\n* jc/pull-training-wheel (2013-06-27) 1 commit\n - pull: require choice between rebase/merge on non-fast-forward pull\n\n Make \"git pull\" refuse with \"it does not fast forward; choose between\n 'pull --merge' and 'pull --rebase'\".\n\n John Keeping seems to want to restrict this to \"git pull\" without\n any other argument. I personally do not have a strong opinion\n either way, but I'm inclined to take such a patch to loosen the new\n logic with other people's support.  Hint, hint...\n\n\n* as/log-output-encoding-in-user-format (2013-07-05) 7 commits\n  (merged to 'next' on 2013-07-05 at d2c99e5)\n + t4041, t4205, t6006, t7102: use iso8859-1 rather than iso-8859-1\n  (merged to 'next' on 2013-07-01 at 3318aa8)\n + t4205: replace .\\+ with ..* in sed commands\n  (merged to 'next' on 2013-06-28 at 4063330)\n + pretty: --format output should honor logOutputEncoding\n + pretty: Add failing tests: --format output should honor logOutputEncoding\n + t4205 (log-pretty-formats): don't hardcode SHA-1 in expected outputs\n + t7102 (reset): don't hardcode SHA-1 in expected outputs\n + t6006 (rev-list-format): don't hardcode SHA-1 in expected outputs\n\n \"log --format=\" did not honor i18n.logoutputencoding configuration\n and this is a beginning of the series that attempts to fix it.\n\n Will merge to 'master'.\n\n\n* jc/maint-diff-core-safecrlf (2013-06-25) 1 commit\n  (merged to 'next' on 2013-07-03 at db8a2a6)\n + diff: demote core.safecrlf=true to core.safecrlf=warn\n\n \"git diff\" refused to even show difference when core.safecrlf is\n set to true (i.e. error out) and there are offending lines in the\n working tree files.\n\n Will merge to 'master'.\n\n\n* jk/fast-import-empty-ls (2013-06-23) 4 commits\n - fast-import: allow moving the root tree\n - fast-import: allow ls or filecopy of the root tree\n - fast-import: set valid mode on root tree in \"ls\"\n - t9300: document fast-import empty path issues\n\n Waiting for reviews.\n $gmane/228741\n\n\n* af/rebase-i-merge-options (2013-07-02) 1 commit\n - Do not ignore merge options in interactive rebase\n\n \"git rebase -i\" now honors --strategy and -X options.\n\n Will merge to 'master'.\n\n\n* rj/cygwin-remove-cheating-lstat (2013-06-25) 1 commit\n - cygwin: Remove the Win32 l/stat() implementation\n\n Seems that this gives different performance results to different\n people.\n\n A replacement WIP has been posted.\n $gmane/229280\n\n\n* jc/triangle-push-fixup (2013-06-24) 5 commits\n  (merged to 'next' on 2013-06-26 at 73cbb69)\n + t/t5528-push-default: test pushdefault workflows\n + t/t5528-push-default: generalize test_push_*\n + push: change `simple` to accommodate triangular workflows\n + config doc: rewrite push.default section\n + t/t5528-push-default: remove redundant test_config lines\n (this branch is tangled with rr/triangle-push-fix.)\n\n Earlier remote.pushdefault (and per-branch branch.*.pushremote)\n were introduced as an additional mechanism to choose what\n repository to push into when \"git push\" did not say it from the\n command line, to help people who push to a repository that is\n different from where they fetch from.  This attempts to finish that\n topic by teaching the default mechanism to choose branch in the\n remote repository to be updated by such a push.\n\n The 'current', 'matching' and 'nothing' modes (specified by the\n push.default configuration variable) extend to such a \"triangular\"\n workflow naturally, but 'upstream' and 'simple' have to be updated.\n\n . 'upstream' is about pushing back to update the branch in the\n remote repository that the current branch fetches from and\n integrates with, it errors out in a triangular workflow.\n\n . 'simple' is meant to help new people by avoiding mistakes, and\n will be the safe default in Git 2.0.  In a non-triangular\n workflow, it will continue to act as a cross between 'upstream'\n and 'current' in that it pushes to the current branch's\n @{upstream} only when it is set to the same name as the current\n branch (e.g. your 'master' forks from the 'master' from the\n central repository).  In a triangular workflow, this series\n tentatively defines it as the same as 'current', but we may have\n to tighten it to avoid surprises in some way.\n\n Will merge to 'master'.\n\n\n* jg/status-config (2013-06-24) 4 commits\n  (merged to 'next' on 2013-07-03 at 6ac1ada)\n + status/commit: make sure --porcelain is not affected by user-facing config\n + commit: make it work with status.short\n + status: introduce status.branch to enable --branch by default\n + status: introduce status.short to enable --short by default\n\n \"git status\" learned status.branch and status.short configuration\n variables to use --branch and --short options by default (override\n with --no-branch and --no-short options from the command line).\n\n The bottom two has been graduated to 'master' but then reverted.\n The tip two are quick attempts to fix the fallout.  The one for\n status.short looks correct; the other one, while it is correct,\n is unfortunately overly complex in order not to introduce an\n unnecessary regression.\n\n Will merge to 'master'.\n\n\n* jc/reflog-doc (2013-06-19) 1 commit\n - setup_reflog_action: document the rules for using GIT_REFLOG_ACTION\n\n Document rules to use GIT_REFLOG_ACTION variable in the scripted\n Porcelain.  git-rebase--interactive locally violates this, but it\n is a leaf user that does not call out to or dot-sources other\n scripts, so fixing it is not all that urgent.\n\n\n* mh/ref-races-optim-invalidate-cached (2013-06-20) 1 commit\n - refs: do not invalidate the packed-refs cache unnecessarily\n\n This requires the platform lstat() to be correct to avoid false\n negatives.\n\n\n* rr/rebase-checkout-reflog (2013-06-17) 5 commits\n  (merged to 'next' on 2013-07-01 at 27cfd27)\n + checkout: respect GIT_REFLOG_ACTION\n  (merged to 'next' on 2013-06-27 at 4d99efa)\n + status: do not depend on rebase reflog messages\n + t/t2021-checkout-last: \"checkout -\" should work after a rebase finishes\n + wt-status: remove unused field in grab_1st_switch_cbdata\n + t7512: test \"detached from\" as well\n (this branch is used by rr/rebase-reflog-message-reword.)\n\n Invocations of \"git checkout\" used internally by \"git rebase\" were\n counted as \"checkout\", and affected later \"git checkout -\" to the\n the user to an unexpected place.\n\n The \"bugfix\" bits of the series is here.  The follow-up part to\n reword reflog messages for steps in \"rebase\" are split to another\n topic.\n\n Will merge to 'master'.\n\n\n* jx/clean-interactive (2013-06-26) 16 commits\n - test: run testcases with POSIX absolute paths on Windows\n - test: add t7301 for git-clean--interactive\n - git-clean: add documentation for interactive git-clean\n - git-clean: add ask each interactive action\n - git-clean: add select by numbers interactive action\n - git-clean: add filter by pattern interactive action\n - git-clean: use a git-add-interactive compatible UI\n - git-clean: add colors to interactive git-clean\n - git-clean: show items of del_list in columns\n - git-clean: add support for -i/--interactive\n  (merged to 'next' on 2013-06-26 at f7be2d8)\n + git-clean: refactor git-clean into two phases\n + write_name{_quoted_relative,}(): remove redundant parameters\n + quote_path_relative(): remove redundant parameter\n + quote.c: substitute path_relative with relative_path\n + path.c: refactor relative_path(), not only strip prefix\n + test: add test cases for relative_path\n\n Add \"interactive\" mode to \"git clean\".\n\n The early part to refactor relative path related helper functions\n looked sensible. The actual \"clean interactive\" may want to be\n discussed further by interested parties before the topic is fully\n merged to 'next'.\n\n\n* jn/add-2.0-u-A-sans-pathspec (2013-04-26) 1 commit\n - git add: -u/-A now affects the entire working tree\n\n Will cook in 'next' until Git 2.0.\n\n\n* jc/core-checkstat-2.0 (2013-05-06) 1 commit\n - core.statinfo: remove as promised in Git 2.0\n\n Will cook in 'next' until Git 2.0.\n\n\n* jc/push-2.0-default-to-simple (2013-06-18) 1 commit\n - push: switch default from \"matching\" to \"simple\"\n\n Will cook in 'next' until Git 2.0.\n\n\n* jc/add-2.0-ignore-removal (2013-04-22) 1 commit\n - git add <pathspec>... defaults to \"-A\"\n\n Updated endgame for \"git add <pathspec>\" that defaults to \"--all\"\n aka \"--no-ignore-removal\".\n\n Will cook in 'next' until Git 2.0.\n"},{"id":"222680","messageId":"20130707003531.GG30132@google.com","threadId":"34352","inReplyTo":"7v4nc98jbc.fsf@alter.siamese.dyndns.org","subject":"Re: What's cooking in git.git (Jul 2013, #02; Fri, 5)","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2013-07-07T00:35:31Z","receivedAt":"2013-07-07T00:35:31Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nJunio C Hamano wrote:\n\n> We are in the middle of 5th week now in the 11-week releace cycle\n> for 1.8.4 (http://tinyurl.com/gitCal), and quite a few topics have\n> graduated to 'master'.  I'd expect the rest of the week to be slow.\n\nI'd like this or the next release to be 2.0, so the common user\ntrouble with \"git push\" pushing more branches than they intended can\nbe over.  Am I crazy?  If not, what can I do to help make it happen?\n\nThanks,\nJonathan\n"},{"id":"222695","messageId":"7vwqp3589v.fsf@alter.siamese.dyndns.org","threadId":"34352","inReplyTo":"20130707003531.GG30132@google.com","subject":"Re: What's cooking in git.git (Jul 2013, #02; Fri, 5)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-07-07T04:00:28Z","receivedAt":"2013-07-07T04:00:28Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jonathan Nieder <jrnieder@gmail.com> writes:\n\n>> We are in the middle of 5th week now in the 11-week releace cycle\n>> for 1.8.4 (http://tinyurl.com/gitCal), and quite a few topics have\n>> graduated to 'master'.  I'd expect the rest of the week to be slow.\n>\n> I'd like this or the next release to be 2.0, so the common user\n> trouble with \"git push\" pushing more branches than they intended can\n> be over.  Am I crazy?  If not, what can I do to help make it happen?\n\nThere are currently three topics slated for 2.0 that changes the\ndefault behaviours in a big way.  The default of the push behaviour\nswitching from matching to simple is one of them, and it has been\nadvertised with advice messages since 1.8.0 (Oct 2012).\n\nThe other two, \"git add -u/-A\" without pathspec to operate on the\nentire tree, and \"git add\" with pathspec acting as if it were given\n\"-A\" option to also record removals to the index, haven't had enough\ntime to be imprinted in users' minds.  The former was only mentioned\nin the release notes of 1.8.2 (Mar 2013), and the advertisement for\nthe latter change appeared first in 1.8.3 (May 2013).\n\nI'd prefer to see users have enough time to adjust to these big\nchanges, at least 6 months (but preferrably 9 months).  I would say\nthat the change to the default \"git push\" behaviour may have had\nenough preparation period, but the other two that are scheduled for\n2.0 is way too young.\n\nWith recent \"triangular\" addition by Ram, the \"simple\" mode, the\nfuture behaviour of \"git push\", was again changed, and has not have\nenough time to mature (isn't it still in 'next'?).\n\nRegarding that \"simple\" thing, I am not sure if the \"if you are\npushing to a remote that is different from where you fetch from, we\ndo exactly the same as 'current'\", which is what we tentatively\nagreed to implement, is safe enough for new people.  I suspect we\nmay want to tighten it a bit more (it would update the branch with\nthe same name as your current local branch, but never try to create\nsuch a branch at the remote, for example).\n\nSo in that sense, even the change to \"git push\" default may not be\nold enough for the upcoming release or the next one.\n"}]}