{"thread":{"id":"3827","subject":"Re: [PATCH] Script for automated historical Git tree grafting","startedAt":"2006-04-08T03:09:36Z","lastAt":"2006-04-08T20:04:12Z","messageCount":2,"participants":["Petr Baudis","Nicholas Miell"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"18462","messageId":"20060408030936.GN27631@pasky.or.cz","threadId":"3827","inReplyTo":"20060406175246.3bd1c972.akpm@osdl.org","subject":"Re: [PATCH] Script for automated historical Git tree grafting","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2006-04-08T03:09:36Z","receivedAt":"2006-04-08T03:09:36Z","isPatch":true,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Fri, Apr 07, 2006 at 02:52:46AM CEST, I got a letter\nwhere Andrew Morton <akpm@osdl.org> said that...\n> Petr Baudis <pasky@suse.cz> wrote:\n> >\n> > This script enables Git users to easily graft the historical Git tree\n> >  (Bitkeeper history import) to the current history.\n> \n> What impact will that have on the (already rather poor) performance of\n> git-whatchanged, gitk, etc?\n\nNegative. ;-)\n\nI didn't try gitk myself, but according to Nick Riviera it eats 1.6G...\nOtherwise, assuming that you have at least git-1.2.5, git-whatchanged on\nthe whole tree should be roughly equally fast as it was before grafting,\nbut git-whatchanged on individual paths is _significantly_ slower.\n\nThat said, 1.3.0rc2 should already have Linus' optimization which should\nfix or at least mitigate the performance hit on narrowed-down\ngit-whatchanged.\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nRight now I am having amnesia and deja-vu at the same time.  I think\nI have forgotten this before.\n"},{"id":"18475","messageId":"1144526652.2337.5.camel@entropy","threadId":"3827","inReplyTo":"20060408030936.GN27631@pasky.or.cz","subject":"Re: [PATCH] Script for automated historical Git tree grafting","fromName":"Nicholas Miell","fromEmail":"nmiell@comcast.net","sentAt":"2006-04-08T20:04:12Z","receivedAt":"2006-04-08T20:04:12Z","isPatch":true,"sender":{"key":"nmiell@comcast.net","avatar":null},"body":"On Sat, 2006-04-08 at 05:09 +0200, Petr Baudis wrote:\n> Dear diary, on Fri, Apr 07, 2006 at 02:52:46AM CEST, I got a letter\n> where Andrew Morton <akpm@osdl.org> said that...\n> > Petr Baudis <pasky@suse.cz> wrote:\n> > >\n> > > This script enables Git users to easily graft the historical Git tree\n> > >  (Bitkeeper history import) to the current history.\n> > \n> > What impact will that have on the (already rather poor) performance of\n> > git-whatchanged, gitk, etc?\n> \n> Negative. ;-)\n> \n> I didn't try gitk myself, but according to Nick Riviera it eats 1.6G...\n> Otherwise, assuming that you have at least git-1.2.5, git-whatchanged on\n> the whole tree should be roughly equally fast as it was before grafting,\n> but git-whatchanged on individual paths is _significantly_ slower.\n> \n> That said, 1.3.0rc2 should already have Linus' optimization which should\n> fix or at least mitigate the performance hit on narrowed-down\n> git-whatchanged.\n\nActually, it ate more than 1.6G -- that was just the resident size, and\nit likes to allocate more memory in between you closing the window and\nit finally exiting (or, you killing it before it OOMs the box, whichever\ncomes first).\n\nqgit has absolutely no problem with the grafted full history, though,\nand those previously mentioned rev-list changes by Linus should fix\ngit-whatchanged.\n\n\n\n\n\n\n\nUnfortunately, this does nothing to fix the disturbing lack of useless\nSimpsons trivia knowledge in the git community. Keith Packard made the\nsame mistake last week.\n\n-- \nNicholas Miell <nmiell@comcast.net>\n"}]}