{"thread":{"id":"3354","subject":"What's in git.git","startedAt":"2006-02-16T06:57:21Z","lastAt":"2006-02-16T06:57:21Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"16248","messageId":"7vk6bvhju6.fsf@assigned-by-dhcp.cox.net","threadId":"3354","inReplyTo":null,"subject":"What's in git.git","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-02-16T06:57:21Z","receivedAt":"2006-02-16T06:57:21Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"* Master branch has these since 1.2.1 maintenance release.\n\n  - documentation fixes:\n    git-commit: Now --only semantics is the default.\n\n  - usability:\n    - rebase aquired a hook to refuse rebasing.\n    - commit and add detects misspelled pathspec while making a partial commit.\n    - git-svnimport: -r adds svn revision number to commit messages\n    - properly git-bisect reset after bisecting from non-master head\n    - send-email: Add some options for controlling how addresses\n      are automatically added to the cc: list.\n    - send-email: Add --cc\n\n* Next branch has these, that are not in master.  If you feel\n  you would benefit from these, testing and feedback is greatly\n  appreciated.\n\n - \"Assume unchanged git\" series (7 commits):\n\n   This was done in response to people on filesystems with slow\n   lstat(2).  I do not have such an environment, so I cannot say\n   I tested it that much.\n\n - \"Rebase to different branch\" (1 commit):\n\n   This was previously discussed on the list.  With this command\n   line:\n\n    \t$ git rebase --onto master~1 master topic\n    \n   would rebase this ancestry graph to:\n    \n              A---B---C topic\n             /\n        D---E---F---G master\n    \n    \n   another graph that looks like this:\n    \n                  A'--B'--C' topic\n                 /\n        D---E---F---G master\n\n   Earlier, you couldn't rebase to anywhere other than on top of\n   \"the other branch\".\n\n\n* Proposed updates \"pu\" branch has these, not in \"next\".  Some\n  of them are of iffy nature, and without further work will not\n  go anywhere.\n\n - \"merge-tree\" series by Linus (2 commits).\n\n   I haven't spent enough time looking at and thinking about\n   this yet.\n\n - \"reuse pack data\" (1 commit).\n\n   I still haven't seen data corruption with this one, which is\n   a good sign, but would like to keep beating it privately for\n   a while.  Perhaps will graduate to \"next\" by next week.\n\n - \"bind commit\" series (6 commits).\n\n   I think the core-side is more or less done with this one.\n   Anybody interested in doing Porcelain side?\n\n - \"shallow clone\" series (1 commit).\n\n   I should drop this one for now and perhaps when enough people\n   are interested reopen the issue.\n"}]}