{"thread":{"id":"38854","subject":"[GSoC Project Help] Unifying git branch -l, git tag -l and git for-each-ref","startedAt":"2015-03-19T11:22:19Z","lastAt":"2015-03-21T17:02:59Z","messageCount":3,"participants":["Sundararajan R","Michael J Gruber","karthik nayak"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"258021","messageId":"loom.20150319T121328-232@post.gmane.org","threadId":"38854","inReplyTo":null,"subject":"[GSoC Project Help] Unifying git branch -l, git tag -l and git for-each-ref","fromName":"Sundararajan R","fromEmail":"dyoucme@gmail.com","sentAt":"2015-03-19T11:22:19Z","receivedAt":"2015-03-19T11:22:19Z","isPatch":false,"sender":{"key":"dyoucme@gmail.com","avatar":null},"body":"Hi all,\n\nI am a Computer Science sophomore at IIT Kanpur. I am interested in \ncontributing to git in GSoC 2015. I have been using git for the past one year \nand am pretty comfortable with its commands which is what made me think about \ncontributing to git. I have attempted the microproject “adding ‘-’ as a \nshorthand to @{-1} in the reset command” [1] [2] from which I learnt about \nhow code is reviewed in the community and how a seemingly small change can \nend up being much more difficult. But the thing I liked the most is the warm \nand welcoming attitude of everyone in the community towards a newcomer like \nme. I wish to take up the project idea “Unifying git branch -l, git tag -l \nand git for-each-ref”. I am in the process of reading and understanding the \ncodes of these three commands and figuring out similarities and differences \nin them. I have gone through some of the discussions regarding this on the \narchive and have also read Junio’s reply to Amate Yolande [3], but I haven’t \nbeen able to find patches which attempt to unify the selection process as \nmentioned in the description of the idea. It would be great if someone could \npoint me towards these patches which would help me when I start designing the \ndetails of the unified implementation. Thanks a lot for your time.\n\nRegards,\nR Sundararajan. \n\n[1] : http://marc.info/?l=git&m=142666740415816&w=2\n[2] : http://marc.info/?l=git&m=142666773315899&w=2\n[3] : http://article.gmane.org/gmane.comp.version-control.git/264966"},{"id":"258023","messageId":"550AC7E9.6060702@drmicha.warpmail.net","threadId":"38854","inReplyTo":"loom.20150319T121328-232@post.gmane.org","subject":"Re: [GSoC Project Help] Unifying git branch -l, git tag -l and git for-each-ref","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2015-03-19T12:58:17Z","receivedAt":"2015-03-19T12:58:17Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Sundararajan R venit, vidit, dixit 19.03.2015 12:22:\n> Hi all,\n> \n> I am a Computer Science sophomore at IIT Kanpur. I am interested in \n> contributing to git in GSoC 2015. I have been using git for the past one year \n> and am pretty comfortable with its commands which is what made me think about \n> contributing to git. I have attempted the microproject “adding ‘-’ as a \n> shorthand to @{-1} in the reset command” [1] [2] from which I learnt about \n> how code is reviewed in the community and how a seemingly small change can \n> end up being much more difficult. But the thing I liked the most is the warm \n> and welcoming attitude of everyone in the community towards a newcomer like \n> me. I wish to take up the project idea “Unifying git branch -l, git tag -l \n> and git for-each-ref”. I am in the process of reading and understanding the \n> codes of these three commands and figuring out similarities and differences \n> in them. I have gone through some of the discussions regarding this on the \n> archive and have also read Junio’s reply to Amate Yolande [3], but I haven’t \n> been able to find patches which attempt to unify the selection process as \n> mentioned in the description of the idea. It would be great if someone could \n> point me towards these patches which would help me when I start designing the \n> details of the unified implementation. Thanks a lot for your time.\n> \n> Regards,\n> R Sundararajan. \n> \n> [1] : http://marc.info/?l=git&m=142666740415816&w=2\n> [2] : http://marc.info/?l=git&m=142666773315899&w=2\n> [3] : http://article.gmane.org/gmane.comp.version-control.git/264966\n\nI don't think there have been actual attempts at unifying the \"display\"\npart of the list modes. A first step would be:\n\nCheck what \"tag -l\" and \"branch -l\" output you can reproduce using\nfor-each-ref format strings.\n\nThen see whether for-each-ref needs to expose more information about the\nrefs.\n\nI wouldn't mind unifying the actual output format, but some will disagree.\n\nAs for the issue of ref selection (contains and such), the following\nthread may be helpful:\n\nhttp://thread.gmane.org/gmane.comp.version-control.git/252472\n\nCheers\nMichael\n"},{"id":"258247","messageId":"550DA443.1030905@gmail.com","threadId":"38854","inReplyTo":"550AC7E9.6060702@drmicha.warpmail.net","subject":"Re: [GSoC Project Help] Unifying git branch -l, git tag -l and git for-each-ref","fromName":"karthik nayak","fromEmail":"karthik.188@gmail.com","sentAt":"2015-03-21T17:02:59Z","receivedAt":"2015-03-21T17:02:59Z","isPatch":false,"sender":{"key":"karthik.188@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1786334?v=4"},"body":"\nOn 03/19/2015 06:28 PM, Michael J Gruber wrote:\n> Sundararajan R venit, vidit, dixit 19.03.2015 12:22:\n> > Hi all,\n> >\n> > I am a Computer Science sophomore at IIT Kanpur. I am interested in\n> > contributing to git in GSoC 2015. I have been using git for the past one year\n> > and am pretty comfortable with its commands which is what made me think about\n> > contributing to git. I have attempted the microproject “adding ‘-’ as a\n> > shorthand to @{-1} in the reset command” [1] [2] from which I learnt about\n> > how code is reviewed in the community and how a seemingly small change can\n> > end up being much more difficult. But the thing I liked the most is the warm\n> > and welcoming attitude of everyone in the community towards a newcomer like\n> > me. I wish to take up the project idea “Unifying git branch -l, git tag -l\n> > and git for-each-ref”. I am in the process of reading and understanding the\n> > codes of these three commands and figuring out similarities and differences\n> > in them. I have gone through some of the discussions regarding this on the\n> > archive and have also read Junio’s reply to Amate Yolande [3], but I haven’t\n> > been able to find patches which attempt to unify the selection process as\n> > mentioned in the description of the idea. It would be great if someone could\n> > point me towards these patches which would help me when I start designing the\n> > details of the unified implementation. Thanks a lot for your time.\n> >\n> > Regards,\n> > R Sundararajan.\n> >\n> > [1] : http://marc.info/?l=git&m=142666740415816&w=2\n> > [2] : http://marc.info/?l=git&m=142666773315899&w=2\n> > [3] : http://article.gmane.org/gmane.comp.version-control.git/264966\n>\n> I don't think there have been actual attempts at unifying the \"display\"\n> part of the list modes. A first step would be:\n>\n> Check what \"tag -l\" and \"branch -l\" output you can reproduce using\n> for-each-ref format strings.\n>\n> Then see whether for-each-ref needs to expose more information about the\n> refs.\n>\n> I wouldn't mind unifying the actual output format, but some will disagree.\n>\n> As for the issue of ref selection (contains and such), the following\n> thread may be helpful:\n>\n> http://thread.gmane.org/gmane.comp.version-control.git/252472\n>\n> Cheers\n> Michael\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n>\nHello,\nI am applying for the same project as well, under GSoC. I found some attempts by\nJeff King towards unification here :\n\nhttps://github.com/peff/git/commits/jk/for-each-ref-contains-wip\n\nWhich was discussed here :\n\nhttp://thread.gmane.org/gmane.comp.version-control.git/230694/focus=2308\n\nHope this helps you out too.\n\nRegards\n-Karthik\n"}]}