{"thread":{"id":"17635","subject":"[ANNOUNCE] GIT 1.6.2-rc0","startedAt":"2009-02-07T21:54:37Z","lastAt":"2009-02-08T09:43:58Z","messageCount":3,"participants":["Junio C Hamano","Matthieu Moy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"103661","messageId":"7vvdrlsyjm.fsf@gitster.siamese.dyndns.org","threadId":"17635","inReplyTo":null,"subject":"[ANNOUNCE] GIT 1.6.2-rc0","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-02-07T21:54:37Z","receivedAt":"2009-02-07T21:54:37Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The 0th release candidate for 1.6.2 is available at the usual places:\n\n http://www.kernel.org/pub/software/scm/git/\n\n git-1.6.2-rc0.tar.{gz,bz2}\t\t\t(source tarball)\n git-htmldocs-1.6.2-rc0.tar.{gz,bz2}\t\t(preformatted docs)\n git-manpages-1.6.2-rc0.tar.{gz,bz2}\t\t(preformatted docs)\n\nThe RPM binary packages for a few architectures are also provided\nas courtesy.\n\n testing/git-*-1.6.2-rc0-1.fc9.$arch.rpm\t(RPM)\n\n----------------------------------------------------------------\n\nGIT v1.6.2 Release Notes (draft)\n================================\n\nWith the next major release, \"git push\" into a branch that is\ncurrently checked out will be refused by default. You can choose\nwhat should happen upon such a push by setting the configuration\nvariable receive.denyCurrentBranch in the receiving repository.\n\nTo ease the transition plan, the receiving repository of such a\npush running this release will issue a big warning when the\nconfiguration variable is missing. Please refer to:\n\n http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007\n\nfor more details on the transition plan.\n\n\nUpdates since v1.6.1\n--------------------\n\n(subsystems)\n\n* git-svn updates.\n\n* gitweb updates, including a new patch view and RSS/Atom feed\n improvements.\n\n* (contrib) git.el updates for better XEmacs compatibility; vc-git.el\n is not shiped with git anymore (it is part of official Emacs)\n\n(performance)\n\n* pack-objects autodetects the number of CPUs available and uses threaded\n version.\n\n(usability, bells and whistles)\n\n* automatic typo correction works on aliases as well\n\n* Initial support for \"git notes\" implemented.\n\n* @{-1} is a way to refer to the last branch you were on. This is\n accepted not only where an object name is expected, but anywhere\n a branch name is expected. E.g. \"git branch --track mybranch @{-1}\"\n \"git rev-parse --symbolic-full-name @{-1}\".\n\n* \"git add -p\" learned 'g'oto action to jump directly to a hunk.\n\n* \"git add -p\" learned to find a hunk with given text with '/'.\n\n* \"git add -p\" optionally can be told to work with just the command letter\n without Enter.\n\n* when \"git am\" stops upon a patch that does not apply, it shows the\n title of the offending patch.\n\n* \"git am --directory=\" and \"git am --reject\" passes these options\n to underlying \"git apply\".\n\n* \"git am\" learned --ignore-date option.\n\n* \"git blame\" aligns author names better when they are spelled in\n non US-ASCII encoding.\n\n* \"git clone\" now makes its best effort when cloning from an empty\n repository to set up configuration variables to refer to the remote\n repository.\n\n* \"git checkout -\" is a shorthand for \"git checkout @{-1}\".\n\n* \"git cherry\" defaults to whatever the current branch is tracking (if\n exists) when the argument is not given.\n\n* \"git cvsserver\" can be told not to add extra \"via git-CVS emulator\" to\n the commit log message it serves via gitcvs.commitmsgannotation\n configuration.\n\n* \"git cvsserver\" learned to handle 'noop' command some CVS clients seem\n to expect to work.\n\n* \"git diff\" learned a new option --inter-hunk-context to coalesce close\n hunks together and show context between them.\n\n* The definition of what constitutes a word for \"git diff --color-words\"\n can be customized via gitattributes, command line or a configuration.\n\n* \"git diff\" learned --patience to run \"patience diff\" algorithm.\n\n* \"git filter-branch\" learned --prune-empty option that discards commits\n that do not change the contents.\n\n* \"git fsck\" now checks loose objects in alternate object stores, instead\n of misreporting them as missing.\n\n* \"git grep -w\" and \"git grep\" for fixed strings have been optimized.\n\n* \"git mergetool\" learned -y(--no-prompt) option to disable prompting.\n\n* \"git rebase -i\" can transplant a history down to root to elsewhere\n with --root option.\n\n* \"git reset --merge\" is a new mode that works similar to the way\n \"git checkout\" switches branches, taking the local changes while\n switching to another commit.\n\n* \"git tag\" learned --contains that works the same way as the same option\n from \"git branch\".\n\n\nFixes since v1.6.1\n------------------\n\nAll of the fixes in v1.6.1.X maintenance series are included in this\nrelease, unless otherwise noted.\n\nHere are fixes that this release has, but have not been backported to\nv1.6.1.X series.\n\n* \"git-add sub/file\" when sub is a submodule incorrectly added the path to\n the superproject.\n\n* \"git bundle\" did not exclude annotated tags even when a range given\n from the command line wanted to.\n\n* \"git filter-branch\" unnecessarily refused to work when you had\n checked out a different commit from what is recorded in the superproject\n index in a submodule.\n\n* \"git filter-branch\" incorrectly tried to update a nonexistent work tree\n at the end when it is run in a bare repository.\n\n* \"git mergetool\" used to ignore autocrlf and other attributes\n based content rewriting.\n\n* branch switching and merges had a silly bug that did not validate\n the correct directory when making sure an existing subdirectory is\n clean.\n\n* \"git -p cmd\" when cmd is not a built-in one left the display in funny state\n when killed in the middle.\n"},{"id":"103699","messageId":"vpqprhte3rs.fsf@bauges.imag.fr","threadId":"17635","inReplyTo":"7vvdrlsyjm.fsf@gitster.siamese.dyndns.org","subject":"Re: [ANNOUNCE] GIT 1.6.2-rc0","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2009-02-08T08:23:03Z","receivedAt":"2009-02-08T08:23:03Z","isPatch":false,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"Junio C Hamano writes:\n\n> GIT v1.6.2 Release Notes (draft)\n> ================================\n>\n> With the next major release, \"git push\" into a branch that is\n> currently checked out will be refused by default. You can choose\n> what should happen upon such a push by setting the configuration\n> variable receive.denyCurrentBranch in the receiving repository.\n\nPerhaps this paragraph should tell _why_ this is a dangerous\noperation. There's probably a better wording, but what about\n\n---- 8< ---\nWith the next major release, \"git push\" into a branch that is\ncurrently checked out will be refused by default: Pushing to a\nchecked-out branch changes the HEAD for this branch, and would confuse\nfurther local operations in the target repository.\n\nYou can choose what should happen [...]\n---- 8< ---\n\n?\n\n-- \nMatthieu\n"},{"id":"103706","messageId":"7vvdrlz2jl.fsf@gitster.siamese.dyndns.org","threadId":"17635","inReplyTo":"vpqprhte3rs.fsf@bauges.imag.fr","subject":"Re: [ANNOUNCE] GIT 1.6.2-rc0","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-02-08T09:43:58Z","receivedAt":"2009-02-08T09:43:58Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Matthieu Moy writes:\n\n> Junio C Hamano writes:\n>\n>> GIT v1.6.2 Release Notes (draft)\n>> ================================\n>>\n>> With the next major release, \"git push\" into a branch that is\n>> currently checked out will be refused by default. You can choose\n>> what should happen upon such a push by setting the configuration\n>> variable receive.denyCurrentBranch in the receiving repository.\n>\n> Perhaps this paragraph should tell _why_ this is a dangerous\n> operation.\n\nI considered it, but that is not what Release Notes is about. It should\nbe a table-of-contents of the highlights in the new release. Interested\nparties can look at the documentation for gory details.\n"}]}