{"thread":{"id":"23890","subject":"[GSoC 2010] The 1st week","startedAt":"2010-05-24T14:57:15Z","lastAt":"2010-05-25T09:06:29Z","messageCount":5,"participants":["Bo Yang","Jeff King","Albert Krawczyk"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"142205","messageId":"AANLkTikSafHBj7VwjwjTVeW3ohL60dOp4sKfZW_vZzCM@mail.gmail.com","threadId":"23890","inReplyTo":null,"subject":"[GSoC 2010] The 1st week","fromName":"Bo Yang","fromEmail":"struggleyb.nku@gmail.com","sentAt":"2010-05-24T14:57:15Z","receivedAt":"2010-05-24T14:57:15Z","isPatch":false,"sender":{"key":"struggleyb.nku@gmail.com","avatar":"https://avatars.githubusercontent.com/u/233030?v=4"},"body":"Hi,\n\n This is the first week of gsoc 2010 coding phrase, and it is a good\ntime to summary the previous work and make a plan for the following\ntwo weeks.\n\nWhat's done:\n1. Get familiar with Git code base and have read the code of 'git\nblame', revision walk, 'git log'.\n2. Try to make some patches for git:\n 1. * by/blame-doc-m-c (2010-05-06) 1 commit, in 'next'\n 2. * by/log-follow (2010-05-10) 4 commits, in 'next'\n 3. the '--graph improvement', in discuss and I think ready for inclusion.\n3. Start to write some code for the line level browser feature. And it\nis in the 'playaround' branch in http://repo.or.cz/w/line.git . Now,\nthe code can parse multiple line ranges for multiple files in only one\nrevision.\n\nWhat's following next 2 weeks:\nIn next 2 weeks, I will try to make up a version of line level browser\nthat supports code modification trace and this version will print all\nthe diff hunks that touch the interesting lines.\n\nRegards!\nBo\n-- \nMy blog: http://blog.morebits.org\n"},{"id":"142236","messageId":"20100525062457.GB10898@coredump.intra.peff.net","threadId":"23890","inReplyTo":"AANLkTikSafHBj7VwjwjTVeW3ohL60dOp4sKfZW_vZzCM@mail.gmail.com","subject":"Re: [GSoC 2010] The 1st week","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2010-05-25T06:24:57Z","receivedAt":"2010-05-25T06:24:57Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, May 24, 2010 at 10:57:15PM +0800, Bo Yang wrote:\n\n> What's done:\n> 1. Get familiar with Git code base and have read the code of 'git\n> blame', revision walk, 'git log'.\n> 2. Try to make some patches for git:\n> 1. * by/blame-doc-m-c (2010-05-06) 1 commit, in 'next'\n> 2. * by/log-follow (2010-05-10) 4 commits, in 'next'\n> 3. the '--graph improvement', in discuss and I think ready for inclusion.\n> 3. Start to write some code for the line level browser feature. And it\n> is in the 'playaround' branch in http://repo.or.cz/w/line.git . Now,\n> the code can parse multiple line ranges for multiple files in only one\n> revision.\n\nYou didn't mention\n\n 4. Contributing to other discussion of --follow on the list.\n\nIt is a small thing, perhaps, but I am very happy to see a GSoC student\nactively participating in the community.\n\nSpeaking of which, I haven't finished polishing the --follow patches\nfrom our earlier thread. I was taking a look at making history\nsimplification (including --parents) work. Are you going to be doing any\nwork on that this summer? If so, I will probably just drop it for now\nand let you deal with it. :)\n\n-Peff\n"},{"id":"142246","messageId":"4BFB7BA7.2080004@anu.edu.au","threadId":"23890","inReplyTo":"15312_1274768714_4BFB6D49_15312_1749_67_20100525062457.GB10898@coredump.intra.peff.net","subject":"Re: [GSoC 2010] The 1st week","fromName":"Albert Krawczyk","fromEmail":"u4232169@anu.edu.au","sentAt":"2010-05-25T07:26:31Z","receivedAt":"2010-05-25T07:26:31Z","isPatch":false,"sender":{"key":"u4232169@anu.edu.au","avatar":null},"body":"On 25/05/2010 4:24 PM, Jeff King wrote:\n> Speaking of which, I haven't finished polishing the --follow patches\n> from our earlier thread. I was taking a look at making history\n> simplification (including --parents) work.\n> \nI've been looking at getting --follow --parents to print correctly, \nhowever the Git code is way over my head. If somebody else smarter then \nme could have a look at that, it would be amazing...\n\nI will keep trying, but I don't know how long it'll take me to get my \nhead around the Git diff generation.\n\nAlbert\n"},{"id":"142257","messageId":"AANLkTilEoK-CZR8C16ageafSnA_TNyp3nXHVAm67_LS3@mail.gmail.com","threadId":"23890","inReplyTo":"20100525062457.GB10898@coredump.intra.peff.net","subject":"Re: [GSoC 2010] The 1st week","fromName":"Bo Yang","fromEmail":"struggleyb.nku@gmail.com","sentAt":"2010-05-25T08:58:11Z","receivedAt":"2010-05-25T08:58:11Z","isPatch":false,"sender":{"key":"struggleyb.nku@gmail.com","avatar":"https://avatars.githubusercontent.com/u/233030?v=4"},"body":"On Tue, May 25, 2010 at 2:24 PM, Jeff King wrote:\n> On Mon, May 24, 2010 at 10:57:15PM +0800, Bo Yang wrote:\n>\n>> What's done:\n>> 1. Get familiar with Git code base and have read the code of 'git\n>> blame', revision walk, 'git log'.\n>> 2. Try to make some patches for git:\n>>     1. * by/blame-doc-m-c (2010-05-06) 1 commit, in 'next'\n>>     2. * by/log-follow (2010-05-10) 4 commits, in 'next'\n>>     3. the '--graph improvement', in discuss and I think ready for inclusion.\n>> 3. Start to write some code for the line level browser feature. And it\n>> is in the 'playaround' branch in http://repo.or.cz/w/line.git . Now,\n>> the code can parse multiple line ranges for multiple files in only one\n>> revision.\n>\n> You didn't mention\n>\n>  4. Contributing to other discussion of --follow on the list.\n>\n> It is a small thing, perhaps, but I am very happy to see a GSoC student\n> actively participating in the community.\n\nThanks! :)\n\n> Speaking of which, I haven't finished polishing the --follow patches\n> from our earlier thread. I was taking a look at making history\n> simplification (including --parents) work. Are you going to be doing any\n> work on that this summer? If so, I will probably just drop it for now\n> and let you deal with it. :)\n\nYeah, the line level browser will touch the parents rewriting things\nand I think the feature of line level history is a super-set of the\n'--follow' things, so you can leave it with me. And in my plan, I will\ncomplete this in next month. :)\n\nRegards!\nBo\n-- \nMy blog: http://blog.morebits.org\n"},{"id":"142266","messageId":"20100525090629.GA30863@coredump.intra.peff.net","threadId":"23890","inReplyTo":"AANLkTilEoK-CZR8C16ageafSnA_TNyp3nXHVAm67_LS3@mail.gmail.com","subject":"Re: [GSoC 2010] The 1st week","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2010-05-25T09:06:29Z","receivedAt":"2010-05-25T09:06:29Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, May 25, 2010 at 04:58:11PM +0800, Bo Yang wrote:\n\n> Yeah, the line level browser will touch the parents rewriting things\n> and I think the feature of line level history is a super-set of the\n> '--follow' things, so you can leave it with me. And in my plan, I will\n> complete this in next month. :)\n\nGreat, I will not worry about the parent rewriting problem, then. I will\nprobably polish and submit the multiple-file follow when I get a chance,\nthough.\n\n-Peff\n"}]}