{"thread":{"id":"27168","subject":"[ANNOUNCE] Git 1.7.5","startedAt":"2011-04-24T20:31:26Z","lastAt":"2011-04-25T10:57:35Z","messageCount":5,"participants":["Junio C Hamano","Sebastien Douche","Jakub Narebski","Ævar Arnfjörð Bjarmason"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"166281","messageId":"7v39l7mlwh.fsf@alter.siamese.dyndns.org","threadId":"27168","inReplyTo":null,"subject":"[ANNOUNCE] Git 1.7.5","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-04-24T20:31:26Z","receivedAt":"2011-04-24T20:31:26Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The latest feature release Git 1.7.5 is available at the usual\nplaces:\n\n http://www.kernel.org/pub/software/scm/git/\n\n git-1.7.5.tar.{gz,bz2}\t\t\t(source tarball)\n git-htmldocs-1.7.5.tar.{gz,bz2}\t\t(preformatted docs)\n git-manpages-1.7.5.tar.{gz,bz2}\t\t(preformatted docs)\n\nThe RPM binary packages for a few architectures are found in:\n\n RPMS/$arch/git-*-1.7.5-1.fc13.$arch.rpm\t(RPM)\n\nThis release has 500+ changes from 70+ contributors; thanks for everybody\nwho contributed.\n\n----------------------------------------------------------------\n\nGit v1.7.5 Release Notes\n========================\n\nUpdates since v1.7.4\n--------------------\n\n * Various MinGW portability fixes.\n\n * Various git-p4 enhancements (in contrib).\n\n * Various vcs-svn, git-svn and gitk enhancements and fixes.\n\n * Various git-gui updates (0.14.0).\n\n * Update to more modern HP-UX port.\n\n * The codebase is getting prepared for i18n/l10n; no translated\n strings nor translation mechanism in the code yet, but the strings\n are being marked for l10n.\n\n * The bash completion script can now complete symmetric difference\n for \"git diff\" command, e.g. \"git diff ...bra\".\n\n * The default minimum length of abbreviated and unique object names\n can now be configured by setting the core.abbrev configuration\n variable.\n\n * \"git apply -v\" reports offset lines when the patch does not apply at\n the exact location recorded in the diff output.\n\n * \"git config\" used to be also known as \"git repo-config\", but the old\n name is now officially deprecated.\n\n * \"git checkout --detach \" is a more user friendly synonym for\n \"git checkout ^0\".\n\n * \"git checkout\" performed on detached HEAD gives a warning and\n advice when the commit being left behind will become unreachable from\n any branch or tag.\n\n * \"git cherry-pick\" and \"git revert\" can be told to use a custom merge\n strategy, similar to \"git rebase\".\n\n * \"git cherry-pick\" remembers which commit failed to apply when it is\n stopped by conflicts, making it unnecessary to use \"commit -c $commit\"\n to conclude it.\n\n * \"git cvsimport\" bails out immediately when the cvs server cannot be\n reached, without spewing unnecessary error messages that complain about\n the server response it never got.\n\n * \"git fetch\" vs \"git upload-pack\" transfer learned 'no-done'\n protocol extension to save one round-trip after the content\n negotiation is done. This saves one HTTP RPC, reducing the overall\n latency for a trivial fetch.\n\n * \"git fetch\" can be told to recursively fetch submodules on-demand.\n\n * \"git grep -f \" learned to treat \"-\" as \"read from the\n standard input stream\".\n\n * \"git grep --no-index\" did not honor pathspecs correctly, returning\n paths outside the specified area.\n\n * \"git init\" learned the --separate-git-dir option to allow the git\n directory for a new repository created elsewhere and linked via the\n gitdir mechanism. This is primarily to help submodule support later\n to switch between a branch of superproject that has the submodule\n and another that does not.\n\n * \"git log\" type commands now understand globbing pathspecs. You\n can say \"git log -- '*.txt'\" for example.\n\n * \"git log\" family of commands learned --cherry and --cherry-mark\n options that can be used to view two diverged branches while omitting\n or highlighting equivalent changes that appear on both sides of a\n symmetric difference (e.g. \"log --cherry A...B\").\n\n * A lazy \"git merge\" that didn't say what to merge used to be an error.\n When run on a branch that has an upstream defined, however, the command\n now merges from the configured upstream.\n\n * \"git mergetool\" learned how to drive \"beyond compare 3\" as well.\n\n * \"git rerere forget\" without pathspec used to forget all the saved\n conflicts that relate to the current merge; it now requires you to\n give it pathspecs.\n\n * \"git rev-list --objects $revs -- $pathspec\" now limits the objects listed\n in its output properly with the pathspec, in preparation for narrow\n clones.\n\n * \"git push\" with no parameters gives better advice messages when\n \"tracking\" is used as the push.default semantics or there is no remote\n configured yet.\n\n * A possible value to the \"push.default\" configuration variable,\n 'tracking', gained a synonym that more naturally describes what it\n does, 'upstream'.\n\n * \"git rerere\" learned a new subcommand \"remaining\" that is similar to\n \"status\" and lists the paths that had conflicts which are known to\n rerere, but excludes the paths that have already been marked as\n resolved in the index from its output. \"git mergetool\" has been\n updated to use this facility.\n\nAlso contains various documentation updates.\n\n\nFixes since v1.7.4\n------------------\n\nAll of the fixes in the v1.7.4.X maintenance series are included in this\nrelease, unless otherwise noted.\n\n * \"git fetch\" from a client that is mostly following the remote\n needlessly told all of its refs to the server for both sides to\n compute the set of objects that need to be transferred efficiently,\n instead of stopping when the server heard enough. In a project with\n many tags, this turns out to be extremely wasteful, especially over\n the smart HTTP transport (sp/maint-{upload,fetch}-pack-stop-early~1).\n\n * \"git fetch\" run from a repository that uses the same repository as\n its alternate object store as the repository it is fetching from\n did not tell the server that it already has access to objects\n reachable from the refs in their common alternate object store,\n causing it to fetch unnecessary objects (jc/maint-fetch-alt).\n\n * \"git remote add --mirror\" created a configuration that is suitable for\n doing both a mirror fetch and a mirror push at the same time, which\n made little sense. We now warn and require the command line to specify\n either --mirror=fetch or --mirror=push.\n"},{"id":"166292","messageId":"BANLkTikhkCDZ5Crw+KGWBprXd6qoFOH8kg@mail.gmail.com","threadId":"27168","inReplyTo":"7v39l7mlwh.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] Git 1.7.5","fromName":"Sebastien Douche","fromEmail":"sdouche@gmail.com","sentAt":"2011-04-25T00:00:28Z","receivedAt":"2011-04-25T00:00:28Z","isPatch":false,"sender":{"key":"sdouche@gmail.com","avatar":"https://gravatar.com/avatar/1b4a6cb11f6237ff9dc78b953ce48e416afa42e947143e14273cdc2c7f6f9c1a?d=mp&s=160"},"body":"On Sun, Apr 24, 2011 at 22:31, Junio C Hamano wrote:\n> The latest feature release Git 1.7.5 is available at the usual\n> places:\n\nGreat! Thank you for this new release. Btw, I've some questions, sorry\nif these seem like frivolous or stupid questions.\n\n>  * The codebase is getting prepared for i18n/l10n; no translated\n>   strings nor translation mechanism in the code yet, but the strings\n>   are being marked for l10n.\n\nWhere are pot files for Git and Gitweb?\n\n>  * \"git checkout --detach \" is a more user friendly synonym for\n>   \"git checkout ^0\".\n\nWhat is the interest?\n\n>  * \"git checkout\" performed on detached HEAD gives a warning and\n>   advice when the commit being left behind will become unreachable from\n>   any branch or tag.\n\nNo sure to understand, it's not already the case?\n\n-- \nSebastien Douche \nTwitter: @sdouche (agile, lean, python, git, open source)\n"},{"id":"166295","messageId":"BANLkTi=77Z-AgBs1YxUvjMS=5dufWMZrNw@mail.gmail.com","threadId":"27168","inReplyTo":"BANLkTikhkCDZ5Crw+KGWBprXd6qoFOH8kg@mail.gmail.com","subject":"Re: [ANNOUNCE] Git 1.7.5","fromName":"Sebastien Douche","fromEmail":"sdouche@gmail.com","sentAt":"2011-04-25T01:07:17Z","receivedAt":"2011-04-25T01:07:17Z","isPatch":false,"sender":{"key":"sdouche@gmail.com","avatar":"https://gravatar.com/avatar/1b4a6cb11f6237ff9dc78b953ce48e416afa42e947143e14273cdc2c7f6f9c1a?d=mp&s=160"},"body":"On Mon, Apr 25, 2011 at 02:00, Sebastien Douche wrote:\n> Great! Thank you for this new release. Btw, I've some questions, sorry\n> if these seem like frivolous or stupid questions.\n\nOk, they are stupid questions :(.\n>\n>>  * The codebase is getting prepared for i18n/l10n; no translated\n>>   strings nor translation mechanism in the code yet, but the strings\n>>   are being marked for l10n.\n>\n> Where are pot files for Git and Gitweb?\n\n$ make pot\n\n>>  * \"git checkout --detach \" is a more user friendly synonym for\n>>   \"git checkout ^0\".\n>\n> What is the interest?\n\nFor inspection (read the doc man).\n\n\n-- \nSebastien Douche \nTwitter: @sdouche (agile, lean, python, git, open source)\n"},{"id":"166305","messageId":"m3oc3uwrja.fsf@localhost.localdomain","threadId":"27168","inReplyTo":"BANLkTikhkCDZ5Crw+KGWBprXd6qoFOH8kg@mail.gmail.com","subject":"Re: [ANNOUNCE] Git 1.7.5","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2011-04-25T10:32:45Z","receivedAt":"2011-04-25T10:32:45Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Sebastien Douche writes:\n\n> On Sun, Apr 24, 2011 at 22:31, Junio C Hamano wrote:\n> > The latest feature release Git 1.7.5 is available at the usual\n> > places:\n> \n> Great! Thank you for this new release. Btw, I've some questions, sorry\n> if these seem like frivolous or stupid questions.\n> \n> >  * The codebase is getting prepared for i18n/l10n; no translated\n> >   strings nor translation mechanism in the code yet, but the strings\n> >   are being marked for l10n.\n> \n> Where are pot files for Git and Gitweb?\n\nActually only programs in C and shell scripts are prepared for\ntranslation. Currently there is no infrastructure for translating\nscripts implemented in Perl... including Git.pm module and gitweb.\n \n> >  * \"git checkout --detach \" is a more user friendly synonym for\n> >   \"git checkout ^0\".\n> \n> What is the interest?\n\nWhat do you mean? \"git checkout ^0\" is quite cryptic way to\ndetach HEAD, and requires deeper knowledge of Git... though I am not\nsure why somebody not knowledgeable in Git might want to detach HEAD\nexplicitly at given commmit / branch.\n\n> >  * \"git checkout\" performed on detached HEAD gives a warning and\n> >   advice when the commit being left behind will become unreachable from\n> >   any branch or tag.\n> \n> No sure to understand, it's not already the case?\n\nIt is reworked to show warning and advice only when it is really\nneeded.\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"166311","messageId":"BANLkTi=P699Rc3Y0KQL5BBY7A_3YhbyDew@mail.gmail.com","threadId":"27168","inReplyTo":"m3oc3uwrja.fsf@localhost.localdomain","subject":"Re: [ANNOUNCE] Git 1.7.5","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2011-04-25T10:57:35Z","receivedAt":"2011-04-25T10:57:35Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Mon, Apr 25, 2011 at 12:32, Jakub Narebski wrote:\n> Sebastien Douche writes:\n>> >  * The codebase is getting prepared for i18n/l10n; no translated\n>> >    strings nor translation mechanism in the code yet, but the strings\n>> >    are being marked for l10n.\n>>\n>> Where are pot files for Git and Gitweb?\n>\n> Actually only programs in C and shell scripts are prepared for\n> translation.  Currently there is no infrastructure for translating\n> scripts implemented in Perl... including Git.pm module and gitweb.\n\nJust the C programs actually, the series for the shell scripts and\nPerl will be resubmitted in the 1.7.6 cycle.\n"}]}