{"thread":{"id":"3963","subject":"[ANNOUNCE] GIT 1.3.1","startedAt":"2006-04-25T08:04:55Z","lastAt":"2006-04-25T08:04:55Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"19084","messageId":"7v1wvm13o8.fsf@assigned-by-dhcp.cox.net","threadId":"3963","inReplyTo":null,"subject":"[ANNOUNCE] GIT 1.3.1","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-04-25T08:04:55Z","receivedAt":"2006-04-25T08:04:55Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The latest maintenance release GIT 1.3.1 is available at the\nusual places:\n\n\thttp://www.kernel.org/pub/software/scm/git/\n\n\tgit-1.3.1.tar.{gz,bz2}\t\t\t(tarball)\n\tRPMS/$arch/git-*-1.3.1-1.$arch.rpm\t(RPM)\n\nJust to let people who are new to the game know, 1.3.X (1<=X)\nseries is purely bugfix maintenance on top of 1.3.0 release, and\nno new features will be added unless there is a compelling\nreason (think of them like 2.6.16.X releases of the kernel,\nslightly looser updates criteria).\n\nThere are four primary branches in git.git repository.\n\n * Releases in the 1.3.X series come from the \"maint\" branch, which\n   was forked at 1.3.0.\n\n * All the new features and improvements start their life as\n   topic branches that are merged to the \"pu\" (proposed updates)\n   branch.  They are often incomplete and/or unstable.  You can\n   think of \"pu\" as the -mm.\n\n * When these topic branches become stable enough, they are\n   merged into \"next\" branch.  I personally run \"next\" branch\n   for my work to trust my data to it, until very close to the\n   next feature release.\n\n * After being cooked for a few days to a week in \"next\", these\n   good changes graduate to the \"master\" branch.  Some of them\n   die while being cooked there, but that does not happen very\n   often (bad apples are culled while in \"pu\").\n\nI make feature release out of \"master\" branch periodically,\nwhich are tagged as X.Y.0 releases.  At that point, \"maint\"\nbranch is forked to prepare X.Y.1 and onward.\n\nIf you are an end user, the \"maint\" releases are the recommended\nstale releases, but you could miss out new features quickly.\nPlease do send in bug reports for them, but do not expect new\ncool features to appear there.\n\nIf you want to stay current and stable, I would recommend to\ntrack \"master\".\n\nIf you are a git developer, being aware of what is happening in\n\"next\" would often be very helpful.  The infrastructure you plan\nto base your change on may be in the process of being updated\nand your changes to \"master\" can become useless when that\nhappens.\n\nIf you are a truly devoted git hacker, picking what is in \"pu\"\ncan be exciting and useful from time to time.\n\nPost 1.3.0 \"master\" branch development currently contains major\nrewrite of log/show/whatchanged infrastructure, and will be\ngetting updated pack-objects, faster write-tree, consolidated\n\"git diff\" that is not a shell script, and hopefully many\nothers.  To reiterate, they will be part of 1.4.0 and no 1.3.X\nseries release will have them.\n\n----------------------------------------------------------------\n\nChanges since v1.3.0 are as follows:\n\nJonas Fonseca:\n      Fix filename scaling for binary files\n\nJunio C Hamano:\n      git-merge: a bit more readable user guidance.\n      pre-commit hook: complain about conflict markers.\n      git-commit --amend: two fixes.\n      pack-objects: do not stop at object that is \"too small\"\n      mailinfo: decode underscore used in \"Q\" encoding properly.\n\nLinus Torvalds:\n      git-log produces no output\n\nNicolas Pitre:\n      fix pack-object buffer size\n\nPaul Mackerras:\n      rev-parse: better error message for ambiguous arguments\n\nPetr Baudis:\n      Document git-var -l listing also configuration variables\n      Document the configuration file\n\nSanti Béjar:\n      Reintroduce svn pools to solve the memory leak.\n\nSerge E. Hallyn:\n      socksetup: don't return on set_reuse_addr() error\n\nShawn Pearce:\n      Document git-clone --reference\n"}]}