{"thread":{"id":"41753","subject":"[GSoC] Introduction and Project Discussion","startedAt":"2016-03-19T17:36:14Z","lastAt":"2016-03-20T15:55:00Z","messageCount":3,"participants":["Chirayu Desai","Thomas Gummerer","Lars Schneider"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"281240","messageId":"CAJj6+1Ewdn_FNHR-qPqYzKEfQ6kgjXRBvc7dzMLK_2pPKukRvg@mail.gmail.com","threadId":"41753","inReplyTo":null,"subject":"[GSoC] Introduction and Project Discussion","fromName":"Chirayu Desai","fromEmail":"chirayudesai1@gmail.com","sentAt":"2016-03-19T17:36:14Z","receivedAt":"2016-03-19T17:36:14Z","isPatch":false,"sender":{"key":"chirayudesai1@gmail.com","avatar":"https://gravatar.com/avatar/c2d0bd062b197c940eaaf3ac349f63fdbe0df58a2421c140ee8c9b4f52af95e3?d=mp&s=160"},"body":"Hi,\n\nI am a first year computer engineering student from India, studying at\nthe Silver Oak College of Engineering and Technology,\nI had already put part of this in \"[PATCH/GSoC] pull: implement\n--[no-]autostash for usage when rebasing\", but at that time I didn't\nnotice that another student was already working on the same change,\nand I would like to apologise for that, it was totally unintentional.\n\nI have since picked another microproject, \"Make “git tag --contains\n<id>” less chatty if is invalid\", and after looking at the code, it\nwould have the same effect for any command with has a \"--with\" or\n\"--contains\" option, which currently are 'tag', 'branch', and\n'for-each-ref'.\n\nI have worked on OSS in the past (and am currently semi-active as\nwell, working as a device maintainer with CyanogenMod, an android\ndistribution)\n\nI would like to work on \"Git remote whitelist/blacklist\". The current\nexample on the ideas page [1] looks like something that wouldn't be\ntoo much trouble to implement. Still need to dig a bit more on that.\n\nI also saw Thomas Gummerer's idea on the list [2], seems like a reflog\non steroids?\nI still don't understand the entirety of that, so some clarity on that\nwould be nice.\nIt also seems a bit complex\n\nApart from this, I was also interested in the \"git config --unset\nimprovement\" idea, as currently something as basic like\n`git config --global foo.bar 1 &&\n git config --global --unset foo.bar`\nleaves a section [foo] in the config.\nI would like to try to solve this in some way without having to\nrewrite the parser, but if that can't be done easily then I'm open to\ndoing it any other way as well.\n\nSo, to sum it up,\nI would like to work on \"Git remote whitelist/blacklist\", and if the\nmentors deem it to not take too much time / not be too hard of a task,\nI could also try to look at the configuration parser.\n\nThanks,\nChirayu Desai\n\n[1]: http://git.github.io/SoC-2016-Ideas/\n[2]: http://article.gmane.org/gmane.comp.version-control.git/286708\n"},{"id":"281274","messageId":"20160320125552.GA32027@hank","threadId":"41753","inReplyTo":"CAJj6+1Ewdn_FNHR-qPqYzKEfQ6kgjXRBvc7dzMLK_2pPKukRvg@mail.gmail.com","subject":"Re: [GSoC] Introduction and Project Discussion","fromName":"Thomas Gummerer","fromEmail":"t.gummerer@gmail.com","sentAt":"2016-03-20T12:55:52Z","receivedAt":"2016-03-20T12:55:52Z","isPatch":false,"sender":{"key":"t.gummerer@gmail.com","avatar":"https://avatars.githubusercontent.com/u/191004?v=4"},"body":"Hi,\n\nOn 03/19, Chirayu Desai wrote:\n> Hi,\n> \n> I am a first year computer engineering student from India, studying at\n> the Silver Oak College of Engineering and Technology,\n> I had already put part of this in \"[PATCH/GSoC] pull: implement\n> --[no-]autostash for usage when rebasing\", but at that time I didn't\n> notice that another student was already working on the same change,\n> and I would like to apologise for that, it was totally unintentional.\n> \n> I have since picked another microproject, \"Make “git tag --contains\n> <id>” less chatty if is invalid\", and after looking at the code, it\n> would have the same effect for any command with has a \"--with\" or\n> \"--contains\" option, which currently are 'tag', 'branch', and\n> 'for-each-ref'.\n> \n> I have worked on OSS in the past (and am currently semi-active as\n> well, working as a device maintainer with CyanogenMod, an android\n> distribution)\n> \n> I would like to work on \"Git remote whitelist/blacklist\". The current\n> example on the ideas page [1] looks like something that wouldn't be\n> too much trouble to implement. Still need to dig a bit more on that.\n> \n> I also saw Thomas Gummerer's idea on the list [2], seems like a reflog\n> on steroids?\n> I still don't understand the entirety of that, so some clarity on that\n> would be nice.\n> It also seems a bit complex\n\nI can't say much about the other projects you mentioned, but my\nproposal is too complex for a GSoC project.  I wrote the idea down to\nconvince myself whether it would be okay or too complex for a GSoC\nproject, but came to the conclusion that it is too complex.  I just\nposted it to the list since I had written it down anyway, in case\nsomeone was interested.  Sorry for the confusion.\n\n> Apart from this, I was also interested in the \"git config --unset\n> improvement\" idea, as currently something as basic like\n> `git config --global foo.bar 1 &&\n>  git config --global --unset foo.bar`\n> leaves a section [foo] in the config.\n> I would like to try to solve this in some way without having to\n> rewrite the parser, but if that can't be done easily then I'm open to\n> doing it any other way as well.\n> \n> So, to sum it up,\n> I would like to work on \"Git remote whitelist/blacklist\", and if the\n> mentors deem it to not take too much time / not be too hard of a task,\n> I could also try to look at the configuration parser.\n> \n> Thanks,\n> Chirayu Desai\n> \n> [1]: http://git.github.io/SoC-2016-Ideas/\n> [2]: http://article.gmane.org/gmane.comp.version-control.git/286708\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\n-- \nThomas\n"},{"id":"281285","messageId":"C1CDE4AB-2175-42D6-BC0A-0900E3AF1852@gmail.com","threadId":"41753","inReplyTo":"CAJj6+1Ewdn_FNHR-qPqYzKEfQ6kgjXRBvc7dzMLK_2pPKukRvg@mail.gmail.com","subject":"Re: [GSoC] Introduction and Project Discussion","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2016-03-20T15:55:00Z","receivedAt":"2016-03-20T15:55:00Z","isPatch":false,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\nOn 19 Mar 2016, at 18:36, Chirayu Desai <chirayudesai1@gmail.com> wrote:\n\n> Hi,\n> \n> I am a first year computer engineering student from India, studying at\n> the Silver Oak College of Engineering and Technology,\n> I had already put part of this in \"[PATCH/GSoC] pull: implement\n> --[no-]autostash for usage when rebasing\", but at that time I didn't\n> notice that another student was already working on the same change,\n> and I would like to apologise for that, it was totally unintentional.\n> \n> I have since picked another microproject, \"Make “git tag --contains\n> <id>” less chatty if is invalid\", and after looking at the code, it\n> would have the same effect for any command with has a \"--with\" or\n> \"--contains\" option, which currently are 'tag', 'branch', and\n> 'for-each-ref'.\n> \n> I have worked on OSS in the past (and am currently semi-active as\n> well, working as a device maintainer with CyanogenMod, an android\n> distribution)\n> \n> I would like to work on \"Git remote whitelist/blacklist\". The current\n> example on the ideas page [1] looks like something that wouldn't be\n> too much trouble to implement. Still need to dig a bit more on that.\n\nThat sounds great. I consider the posted idea as just something to get\nyou started. If you see ways to improve the idea then I would be super\ninterested. E.g. we might need a mechanism for exceptions (either\npermanently in the config or via command line flag).\n\n- Lars\n\n> \n> I also saw Thomas Gummerer's idea on the list [2], seems like a reflog\n> on steroids?\n> I still don't understand the entirety of that, so some clarity on that\n> would be nice.\n> It also seems a bit complex\n> \n> Apart from this, I was also interested in the \"git config --unset\n> improvement\" idea, as currently something as basic like\n> `git config --global foo.bar 1 &&\n> git config --global --unset foo.bar`\n> leaves a section [foo] in the config.\n> I would like to try to solve this in some way without having to\n> rewrite the parser, but if that can't be done easily then I'm open to\n> doing it any other way as well.\n> \n> So, to sum it up,\n> I would like to work on \"Git remote whitelist/blacklist\", and if the\n> mentors deem it to not take too much time / not be too hard of a task,\n> I could also try to look at the configuration parser.\n> \n> Thanks,\n> Chirayu Desai\n> \n> [1]: http://git.github.io/SoC-2016-Ideas/\n> [2]: http://article.gmane.org/gmane.comp.version-control.git/286708\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"}]}