{"thread":{"id":"21833","subject":"[ANNOUNCE] GIT 1.6.6.rc1","startedAt":"2009-12-02T23:24:22Z","lastAt":"2009-12-02T23:24:22Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"129086","messageId":"7veind7ye1.fsf@alter.siamese.dyndns.org","threadId":"21833","inReplyTo":null,"subject":"[ANNOUNCE] GIT 1.6.6.rc1","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-12-02T23:24:22Z","receivedAt":"2009-12-02T23:24:22Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"A release candidate GIT 1.6.6.rc1 is available at the usual places\nfor testing:\n\n  http://www.kernel.org/pub/software/scm/git/\n\n  git-1.6.6.rc1.tar.{gz,bz2}\t\t\t(source tarball)\n  git-htmldocs-1.6.6.rc1.tar.{gz,bz2}\t\t(preformatted docs)\n  git-manpages-1.6.6.rc1.tar.{gz,bz2}\t\t(preformatted docs)\n\nThe RPM binary packages for a few architectures are found in:\n\n  testing/git-*-1.6.6.rc1-1.fc11.$arch.rpm\t(RPM)\n\nGit v1.6.6 Release Notes (draft)\n================================\n\nNotes on behaviour change\n-------------------------\n\n * In this release, \"git fsck\" defaults to \"git fsck --full\" and\n   checks packfiles, and because of this it will take much longer to\n   complete than before.  If you prefer a quicker check only on loose\n   objects (the old default), you can say \"git fsck --no-full\".  This\n   has been supported by 1.5.4 and newer versions of git, so it is\n   safe to write it in your script even if you use slightly older git\n   on some of your machines.\n\nPreparing yourselves for compatibility issues in 1.7.0\n------------------------------------------------------\n\nIn git 1.7.0, which is planned to be the release after 1.6.6, there will\nbe a handful of behaviour changes that will break backward compatibility.\n\nThese changes were discussed long time ago and existing behaviours have\nbeen identified as more problematic to the userbase than keeping them for\nthe sake of backward compatibility.\n\nWhen necessary, transition strategy for existing users has been designed\nnot to force them running around setting configuration variables and\nupdating their scripts in order to either keep the traditional behaviour\nor use the new behaviour on the day their sysadmin decides to install\nthe new version of git.  When we switched from \"git-foo\" to \"git foo\" in\n1.6.0, even though the change had been advertised and the transition\nguide had been provided for a very long time, the users procrastinated\nduring the entire transtion period, and ended up panicking on the day\ntheir sysadmins updated their git installation.  We tried very hard to\navoid repeating that unpleasantness.\n\nFor changes decided to be in 1.7.0, we have been much louder to strongly\ndiscourage such procrastination.  If you have been using recent versions\nof git, you would have already seen warnings issued when you exercised\nfeatures whose behaviour will change, with the instruction on how to\nkeep the existing behaviour if you want to.  You hopefully should be\nwell prepared already.\n\nOf course, we have also given \"this and that will change in 1.7.0;\nprepare yourselves\" warnings in the release notes and announcement\nmessages.  Let's see how well users will fare this time.\n\n * \"git push\" into a branch that is currently checked out (i.e. pointed by\n   HEAD in a repository that is not bare) will be refused by default.\n\n   Similarly, \"git push $there :$killed\" to delete the branch $killed\n   in a remote repository $there, when $killed branch is the current\n   branch pointed at by its HEAD, will be refused by default.\n\n   Setting the configuration variables receive.denyCurrentBranch and\n   receive.denyDeleteCurrent to 'ignore' in the receiving repository\n   can be used to override these safety features.  Versions of git\n   since 1.6.2 have issued a loud warning when you tried to do them\n   without setting the configuration, so repositories of people who\n   still need to be able to perform such a push should already have\n   been future proofed.\n\n   Please refer to:\n\n   http://git.or.cz/gitwiki/GitFaq#non-bare\n   http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007\n\n   for more details on the reason why this change is needed and the\n   transition process that already took place so far.\n\n * \"git send-email\" will not make deep threads by default when sending a\n   patch series with more than two messages.  All messages will be sent\n   as a reply to the first message, i.e. cover letter.  Git 1.6.6 (this\n   release) will issue a warning about the upcoming default change, when\n   it uses the traditional \"deep threading\" behaviour as the built-in\n   default.  To squelch the warning but still use the \"deep threading\"\n   behaviour, give --chain-reply-to option or set sendemail.chainreplyto\n   to true.\n\n   It has been possible to configure send-email to send \"shallow thread\"\n   by setting sendemail.chainreplyto configuration variable to false.\n   The only thing 1.7.0 release will do is to change the default when\n   you haven't configured that variable.\n\n * \"git status\" will not be \"git commit --dry-run\".  This change does not\n   affect you if you run the command without pathspec.\n\n   Nobody sane found the current behaviour of \"git status Makefile\" useful\n   nor meaningful, and it confused users.  \"git commit --dry-run\" has been\n   provided as a way to get the current behaviour of this command since\n   1.6.5.\n\n * \"git diff\" traditionally treated various \"ignore whitespace\" options\n   only as a way to filter the patch output.  \"git diff --exit-code -b\"\n   exited with non-zero status even if all changes were about changing the\n   ammount of whitespace and nothing else.  and \"git diff -b\" showed the\n   \"diff --git\" header line for such a change without patch text.\n\n   In 1.7.0, the \"ignore whitespaces\" will affect the semantics of the\n   diff operation itself.  A change that does not affect anything but\n   whitespaces will be reported with zero exit status when run with\n   --exit-code, and there will not be \"diff --git\" header for such a\n   change.\n\n\nUpdates since v1.6.5\n--------------------\n\n(subsystems)\n\n * various git-gui updates including new translations, wm states, etc.\n\n * git-svn updates.\n\n * \"git fetch\" over http learned a new mode that is different from the\n   traditional \"dumb commit walker\".\n\n(portability)\n\n * imap-send can be built on mingw port.\n\n(performance)\n\n * \"git diff -B\" has smaller memory footprint.\n\n(usability, bells and whistles)\n\n * The object replace mechanism can be bypassed with --no-replace-objects\n   global option given to the \"git\" program.\n\n * In configuration files, a few variables that name paths can begin with ~/\n   and ~username/ and they are expanded as expected.\n\n * \"git subcmd -h\" now shows short usage help for many more subcommands.\n\n * \"git bisect reset\" can reset to an arbitrary commit.\n\n * \"git checkout frotz\" when there is no local branch \"frotz\" but there\n   is only one remote tracking branch \"frotz\" is taken as a request to\n   start the named branch at the corresponding remote tracking branch.\n\n * \"git commit -c/-C/--amend\" can be told with a new \"--reset-author\" option\n   to ignore authorship information in the commit it is taking the message\n   from.\n\n * \"git describe\" can be told to add \"-dirty\" suffix with \"--dirty\" option.\n\n * \"git diff\" learned --submodule option to show a list of one-line logs\n   instead of differences between the commit object names.\n\n * \"git diff\" learned to honor diff.color.func configuration to paint\n   function name hint printed on the hunk header \"@@ -j,k +l,m @@\" line\n   in the specified color.\n\n * \"git fetch\" learned --all and --multiple options, to run fetch from\n   many repositories, and --prune option to remove remote tracking\n   branches that went stale.  These make \"git remote update\" and \"git\n   remote prune\" less necessary (there is no plan to remove \"remote\n   update\" nor \"remote prune\", though).\n\n * \"git fsck\" by default checks the packfiles (i.e. \"--full\" is the\n   default); you can turn it off with \"git fsck --no-full\".\n\n * \"git grep\" can use -F (fixed strings) and -i (ignore case) together.\n\n * import-tars contributed fast-import frontend learned more types of\n   compressed tarballs.\n\n * \"git instaweb\" knows how to talk with mod_cgid to apache2.\n\n * \"git log --decorate\" shows the location of HEAD as well.\n\n * \"git log\" and \"git rev-list\" learned to take revs and pathspecs from\n   the standard input with the new \"--stdin\" option.\n\n * \"--pretty=format\" option to \"log\" family of commands learned:\n\n   . to wrap text with the \"%w()\" specifier.\n   . to show reflog information with \"%g[sdD]\" specifier.\n\n * \"git notes\" command to annotate existing commits.\n\n * \"git merge\" (and \"git pull\") learned --ff-only option to make it fail\n   if the merge does not result in a fast-forward.\n\n * The ancient \"git merge <message> HEAD <branch>...\" syntax will be\n   removed in later versions of git.  A warning is given and tells\n   users to use the \"git merge -m <message> <branch>...\" instead.\n\n * \"git mergetool\" learned to use p4merge.\n\n * \"git rebase -i\" learned \"reword\" that acts like \"edit\" but immediately\n   starts an editor to tweak the log message without returning control to\n   the shell, which is done by \"edit\" to give an opportunity to tweak the\n   contents.\n\n * \"git send-email\" can be told with \"--envelope-sender=auto\" to use the\n   same address as \"From:\" address as the envelope sender address.\n\n * \"git send-email\" will issue a warning when it defaults to the\n   --chain-reply-to behaviour without being told by the user and\n   instructs to prepare for the change of the default in 1.7.0 release.\n\n * In \"git submodule add <repository> <path>\", <path> is now optional and\n   inferred from <repository> the same way \"git clone <repository>\" does.\n\n * \"git svn\" learned to read SVN 1.5+ and SVK merge tickets.\n\n * \"gitweb\" can optionally render its \"blame\" output incrementally (this\n   requires JavaScript on the client side).\n\n * Author names shown in gitweb output are links to search commits by the\n   author.\n\nFixes since v1.6.5\n------------------\n\nAll of the fixes in v1.6.5.X maintenance series are included in this\nrelease, unless otherwise noted.\n\n * Enumeration of available merge strategies iterated over the list of\n   commands in a wrong way, sometimes producing an incorrect result.\n   Will backport by merging ed87465 (builtin-merge.c: call\n   exclude_cmds() correctly., 2009-11-25).\n\n * \"git format-patch revisions... -- path\" issued an incorrect error\n   message that suggested to use \"--\" on the command line when path\n   does not exist in the current work tree (it is a separate matter if\n   it makes sense to limit format-patch with pathspecs like that\n   without using the --full-diff option).  Will backport by merging\n   7e93d3b (format-patch: add test for parsing of \"--\", 2009-11-26).\n\n * \"git shortlog\" did not honor the \"encoding\" header embedded in the\n   commit object like \"git log\" did.  Will backport by merging 79f7ca0\n   (shortlog: respect commit encoding, 2009-11-25).\n\n----------------------------------------------------------------\n\nChanges since v1.6.6-rc0 are as follows:\n\nAvery Pennarun (1):\n      builtin-merge.c: call exclude_cmds() correctly.\n\nBenjamin Kramer (1):\n      Explicitly truncate bswap operand to uint32_t\n\nBert Wesarg (2):\n      Give the hunk comment its own color\n      get_ref_states: strdup entries and free util in stale list\n\nBjörn Gustavsson (11):\n      Teach the --all option to 'git fetch'\n      Teach the --multiple option to 'git fetch'\n      Add the configuration option skipFetchAll\n      Add missing test for 'git remote update --prune'\n      Re-implement 'git remote update' using 'git fetch'\n      Clarify and correct -z\n      apply: apply works outside a repository\n      apply: Format all options using back-quotes\n      apply: Use the term \"working tree\" consistently\n      Fix over-simplified documentation for 'git log -z'\n      gitworkflows: Consistently back-quote git commands\n\nBrian Gernhardt (1):\n      t/gitweb-lib: Split HTTP response with non-GNU sed\n\nChristian Couder (6):\n      Documentation: add \"Fighting regressions with git bisect\" article\n      replace: use a GIT_NO_REPLACE_OBJECTS env variable\n      Documentation: fix typos and spelling in replace documentation\n      Documentation: talk a little bit about GIT_NO_REPLACE_OBJECTS\n      bisect: simplify calling visualizer using '--bisect' option\n      Documentation: update descriptions of revision options related to '--bisect'\n\nDavid Aguilar (1):\n      help: Do not unnecessarily look for a repository\n\nDavid Soria Parra (1):\n      Documentation: Document --branch option in git clone synopsis\n\nErick Mattos (1):\n      commit -c/-C/--amend: reset timestamp and authorship to committer with --reset-author\n\nFelipe Contreras (3):\n      format-patch: fix parsing of \"--\" on the command line\n      format-patch: add test for parsing of \"--\"\n      send-email: automatic envelope sender\n\nHorst H. von Brand (1):\n      git-pull.sh: Fix call to git-merge for new command format\n\nJakub Narebski (10):\n      gitweb: Add optional \"time to generate page\" info in footer\n      gitweb: Incremental blame (using JavaScript)\n      gitweb: Colorize 'blame_incremental' view during processing\n      gitweb: Create links leading to 'blame_incremental' using JavaScript\n      gitweb: Minify gitweb.js if JSMIN is defined\n      t/gitweb-lib.sh: Split gitweb output into headers and body\n      gitweb: Document current snapshot rules via new tests\n      gitweb.js: Harden setting blamed commit info in incremental blame\n      gitweb: Make linking to actions requiring JavaScript a feature\n      gitweb: Add link to other blame implementation in blame views\n\nJay Soffian (4):\n      remote: refactor some logic into get_stale_heads()\n      teach warn_dangling_symref to take a FILE argument\n      builtin-fetch: add --prune option\n      builtin-fetch: add --dry-run option\n\nJeff King (1):\n      prune-packed: only show progress when stderr is a tty\n\nJohannes Sixt (2):\n      t4014-format-patch: do not assume 'test' is available as non-builtin\n      Add a notice that only certain functions can print color escape codes\n\nJonathan Nieder (1):\n      Makefile: do not clean arm directory\n\nJunio C Hamano (19):\n      mailinfo: -b option keeps [bracketed] strings that is not a [PATCH] marker\n      Pretty-format: %[+-]x to tweak inter-item newlines\n      read_revision_from_stdin(): use strbuf\n      Teach --stdin option to \"log\" family\n      setup_revisions(): do not call get_pathspec() too early\n      Make --stdin option to \"log\" family read also pathspecs\n      t9001: test --envelope-sender option of send-email\n      Add trivial tests for --stdin option to log family\n      Protect scripted Porcelains from GREP_OPTIONS insanity\n      builtin-apply.c: pay attention to -p<n> when determining the name\n      Remove dead code from \"git am\"\n      emit_line(): don't emit an empty <SET><RESET> followed by a newline\n      Update draft release notes to 1.6.6 before merging topics for -rc1\n      git-merge: a deprecation notice of the ancient command line syntax\n      Update draft release notes to 1.6.6 before -rc1\n      Do not misidentify \"git merge foo HEAD\" as an old-style invocation\n      merge: do not add standard message when message is given with -m option\n      Prepare for 1.6.5.4\n      Git 1.6.6-rc1\n\nMark Rada (2):\n      gitweb: check given hash before trying to create snapshot\n      gitweb: Smarter snapshot names\n\nMartin Storsjö (3):\n      Disable CURLOPT_NOBODY before enabling CURLOPT_PUT and CURLOPT_POST\n      Refactor winsock initialization into a separate function\n      Enable support for IPv6 on MinGW\n\nMatthew Ogilvie (5):\n      cvsserver doc: database generally can not be reproduced consistently\n      config documentation: some configs are auto-set by git-init\n      t2300: use documented technique to invoke git-sh-setup\n      t3409 t4107 t7406 t9150: use dashless commands\n      t/README: Document GIT_TEST_INSTALLED and GIT_TEST_EXEC_PATH\n\nMatthieu Moy (4):\n      merge-recursive: point the user to commit when file would be overwritten.\n      user-manual: Document that \"git merge\" doesn't like uncommited changes.\n      merge-recursive: make the error-message generation an extern function\n      builtin-merge: show user-friendly error messages for fast-forward too.\n\nMichael J Gruber (1):\n      Documentation: Fix a few i.e./e.g. mix-ups\n\nNanako Shiraishi (2):\n      t1200: fix a timing dependent error\n      prepare send-email for smoother change of --chain-reply-to default\n\nNicolas Pitre (1):\n      pack-objects: split implications of --all-progress from progress activation\n\nRamsay Allan Jones (1):\n      git-count-objects: Fix a disk-space under-estimate on Cygwin\n\nRené Scharfe (2):\n      strbuf_add_wrapped_text(): skip over colour codes\n      mergetool--lib: simplify guess_merge_tool()\n\nStephen Boyd (3):\n      gitweb.js: fix null object exception in initials calculation\n      instaweb: restart server if already running\n      gitweb.js: fix padLeftStr() and its usage\n\nTay Ray Chuan (1):\n      remote-curl.c: fix rpc_out()\n\nUwe Kleine-König (1):\n      shortlog: respect commit encoding\n"}]}