{"thread":{"id":"7868","subject":"What's cooking in git.git (topics)","startedAt":"2007-04-27T08:24:24Z","lastAt":"2007-05-06T08:53:24Z","messageCount":5,"participants":["Junio C Hamano","Linus Torvalds"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"40576","messageId":"11776622643639-git-send-email-junkio@cox.net","threadId":"7868","inReplyTo":"11776622643106-git-send-email-junkio@cox.net","subject":"What's cooking in git.git (topics)","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-04-27T08:24:24Z","receivedAt":"2007-04-27T08:24:24Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here are the topics that have been cooking. Commits prefixed\nwith '-' are only in 'pu' while commits prefixed with '+' are\nin 'next'. The topics list the commits in reverse chronological\norder.\n\n* jc/attr (Sat Apr 21 03:14:13 2007 -0700) 2 commits\n + Add 'filter' attribute and external filter driver definition.\n + Add 'ident' conversion.\n\nAs two people on the list whose judgement on design issues I\ntrust both say \"give them rope is Ok\", perhaps I should push\nthis out to 'master' before v1.5.2-rc1. I am still worried\nabout the rope being too long, though, and tried to describe the\nintent and limitation in the documentation to prevent users from\nhurting themselves, but I do not think the descriptions I have\nare good enough yet.\n\n* jc/blame (Fri Apr 27 00:42:15 2007 -0700) 7 commits\n - Apply mailmap in git-blame output.\n - Split out mailmap handling out of shortlog\n - blame: show log as it goes\n - git-blame: optimize get_origin() from linear search to hash-\n lookup.\n - git-blame: pass \"struct scoreboard *\" pointers around.\n - blame: lift structure definitions up\n - blame -s: suppress author name and time.\n\nIn addition to the update to use .mailmap, this has the \"log\"\noutput that uses the blame machinery Linus suggested. I think I\nknow what more are needed to make it more pleasant to use, but\nthe necessary changes seem a bit too involved. I might advance\nthe topic a bit more during the stabilization period for v1.5.2,\nbut I am planning to leave the actual merge until v1.5.3 cycle.\n\n* lt/objalloc (Mon Apr 16 22:13:09 2007 -0700) 1 commit\n - Make the object lookup hash use a \"object index\" instead of a\n pointer\n* jc/diff (Mon Dec 25 01:08:50 2006 -0800) 2 commits\n - test-para: combined diff between HEAD, index and working tree.\n - para-walk: walk n trees, index and working tree in parallel\n\nThese are stalled.\n"},{"id":"40707","messageId":"7v3b2jdo9h.fsf@assigned-by-dhcp.cox.net","threadId":"7868","inReplyTo":"11776622643639-git-send-email-junkio@cox.net","subject":"What's cooking in git.git (topics)","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-04-29T18:33:14Z","receivedAt":"2007-04-29T18:33:14Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here are the topics that have been cooking. Commits prefixed\nwith '-' are only in 'pu' while commits prefixed with '+' are\nin 'next'. The topics list the commits in reverse chronological\norder.\n\nWell, everything meant for v1.5.2 is in 'master' now. There is\nnothing to see here.\n\n* jc/blame (Fri Apr 20 16:25:50 2007 -0700) 4 commits\n - blame: show log as it goes\n - git-blame: optimize get_origin() from linear search to hash-\n lookup.\n - git-blame: pass \"struct scoreboard *\" pointers around.\n - blame: lift structure definitions up\n* lt/objalloc (Mon Apr 16 22:13:09 2007 -0700) 1 commit\n - Make the object lookup hash use a \"object index\" instead of a\n pointer\n* jc/diff (Mon Dec 25 01:08:50 2006 -0800) 2 commits\n - test-para: combined diff between HEAD, index and working tree.\n - para-walk: walk n trees, index and working tree in parallel\n"},{"id":"40709","messageId":"alpine.LFD.0.98.0704291142510.9964@woody.linux-foundation.org","threadId":"7868","inReplyTo":"7v3b2jdo9h.fsf@assigned-by-dhcp.cox.net","subject":"Re: What's cooking in git.git (topics)","fromName":"Linus Torvalds","fromEmail":"torvalds@linux-foundation.org","sentAt":"2007-04-29T18:45:49Z","receivedAt":"2007-04-29T18:45:49Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Sun, 29 Apr 2007, Junio C Hamano wrote:\n>\n> * lt/objalloc (Mon Apr 16 22:13:09 2007 -0700) 1 commit\n> - Make the object lookup hash use a \"object index\" instead of a\n> pointer\n\nI think you should just drop this. \n\nYou merged the two patches that made this possible, and the third in the \nseries isn't really worth it. I can re-create it at will (maybe better) \nnow that the core object allocations are all cleaned up, and that patch \nsimply didn't give enough of an advantage to be worth it.\n\nMaybe inlining the object index -> ptr conversion would have solved the \nperformance regression, but it migth also be something more fundamental, \nlike the potential extra cache miss in the converstion part (when looking \nup the allocation block).\n\nSo it was interesting to try, but I don't think it's worth carrying around \nconsidering the results.\n\n\t\tLinus\n"},{"id":"40771","messageId":"7vlkg9bga6.fsf@assigned-by-dhcp.cox.net","threadId":"7868","inReplyTo":"alpine.LFD.0.98.0704291142510.9964@woody.linux-foundation.org","subject":"Re: What's cooking in git.git (topics)","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-04-30T23:20:49Z","receivedAt":"2007-04-30T23:20:49Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Linus Torvalds writes:\n\n> On Sun, 29 Apr 2007, Junio C Hamano wrote:\n>>\n>> * lt/objalloc (Mon Apr 16 22:13:09 2007 -0700) 1 commit\n>> - Make the object lookup hash use a \"object index\" instead of a\n>> pointer\n>\n> I think you should just drop this. \n\nYeah. I was mostly concentrating on maint/master for the past\nseveral days, and blindly carrying it around was cheaper than\ndeciding to drop it in my workflow.\n"},{"id":"41196","messageId":"7vd51ecozf.fsf@assigned-by-dhcp.cox.net","threadId":"7868","inReplyTo":"7v3b2jdo9h.fsf@assigned-by-dhcp.cox.net","subject":"What's cooking in git.git (topics)","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-05-06T08:53:24Z","receivedAt":"2007-05-06T08:53:24Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here are the topics that have been cooking. Commits prefixed\nwith '-' are only in 'pu' while commits prefixed with '+' are\nin 'next'. The topics list the commits in reverse chronological\norder.\n\nAs I have been sick and am mostly concentrating on fixes on\n'master' anyway, there aren't much to see here. Indeed,\n'master' and 'next' still have identical trees.\n\n* fl/cvsserver (Wed May 2 02:45:22 2007 +0200) 1 commit\n - cvsserver: Add test cases for git-cvsserver\n\nI need to ask k.org people to install sqlite and\nlibdvd-sqlite-perl before I can advance this to 'next'.\n\n* jc/blame (Fri Apr 20 16:25:50 2007 -0700) 4 commits\n - blame: show log as it goes\n - git-blame: optimize get_origin() from linear search to hash-\n lookup.\n - git-blame: pass \"struct scoreboard *\" pointers around.\n - blame: lift structure definitions up\n"}]}