{"thread":{"id":"7150","subject":"[PATCH] shortlog: prompt when reading from terminal by mistake","startedAt":"2007-03-08T10:12:06Z","lastAt":"2007-03-10T00:39:40Z","messageCount":17,"participants":["Junio C Hamano","Johannes Schindelin","Shawn O. Pearce","Alex Riesen","Linus Torvalds","Matthieu Moy","Jakub Narebski"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"36612","messageId":"7vhcsw9h8p.fsf@assigned-by-dhcp.cox.net","threadId":"7150","inReplyTo":null,"subject":"[PATCH] shortlog: prompt when reading from terminal by mistake","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-03-08T10:12:06Z","receivedAt":"2007-03-08T10:12:06Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"I was trying to see who have been active recently to find GSoC\nmentor candidates by running:\n\n\t$ git shortlog -s -n --since=4.months | head -n 20\n\nAfter waiting for about 20 seconds, I started getting worried,\nthinking that the recent revision traversal updates might have\nhad an unintended side effect.\n\nNot so. \"git shortlog\" acts as a filter when no revs are given,\nunlike \"git log\" which defaults to HEAD. It was reading from\nits standard input.\n\nSigned-off-by: Junio C Hamano \n---\n\n Arguably because --since=4.months clearly states I am\n expecting it to start digging from somewhere, it would be\n more sensible to default to HEAD in this case. I suspect it\n might be as simple as checking argc before we call\n setup_revisions() and pass \"HEAD\" as the default parameter to\n it, but it is getting late here.\n\n builtin-shortlog.c | 5 ++++-\n 1 files changed, 4 insertions(+), 1 deletions(-)\n\ndiff --git a/builtin-shortlog.c b/builtin-shortlog.c\nindex 2d7726e..29343ae 100644\n--- a/builtin-shortlog.c\n+++ b/builtin-shortlog.c\n@@ -304,8 +304,11 @@ int cmd_shortlog(int argc, const char **argv, const char *prefix)\n \tif (!access(\".mailmap\", R_OK))\n \t\tread_mailmap(\".mailmap\");\n \n-\tif (rev.pending.nr == 0)\n+\tif (rev.pending.nr == 0) {\n+\t\tif (isatty(0))\n+\t\t\tfprintf(stderr, \"(reading log to summarize from standard input)\\n\");\n \t\tread_from_stdin(&list);\n+\t}\n \telse\n \t\tget_from_rev(&rev, &list);\n \n"},{"id":"36619","messageId":"Pine.LNX.4.63.0703081344140.22628@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"7150","inReplyTo":"7vhcsw9h8p.fsf@assigned-by-dhcp.cox.net","subject":"Re: [PATCH] shortlog: prompt when reading from terminal by mistake","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-03-08T13:04:04Z","receivedAt":"2007-03-08T13:04:04Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 8 Mar 2007, Junio C Hamano wrote:\n\n> I was trying to see who have been active recently to find GSoC\n> mentor candidates by running:\n> \n> \t$ git shortlog -s -n --since=4.months | head -n 20\n> \n> After waiting for about 20 seconds, I started getting worried,\n> thinking that the recent revision traversal updates might have\n> had an unintended side effect.\n> \n> Not so. \"git shortlog\" acts as a filter when no revs are given,\n> unlike \"git log\" which defaults to HEAD. It was reading from\n> its standard input.\n> \n> Signed-off-by: Junio C Hamano \n\nAcked-by: Johannes Schindelin \n\n> Arguably because --since=4.months clearly states I am\n> expecting it to start digging from somewhere, it would be\n> more sensible to default to HEAD in this case. I suspect it\n> might be as simple as checking argc before we call\n> setup_revisions() and pass \"HEAD\" as the default parameter to\n> it, but it is getting late here.\n\nHm. Better check argc _afterwards_, and if it changed, but no pending \nobject was there, add \"HEAD\".\n\nCiao,\nDscho\n"},{"id":"36625","messageId":"20070308150756.GB30674@spearce.org","threadId":"7150","inReplyTo":"7vhcsw9h8p.fsf@assigned-by-dhcp.cox.net","subject":"Re: GSoC project mentors","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-03-08T15:07:56Z","receivedAt":"2007-03-08T15:07:56Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Junio C Hamano wrote:\n> I was trying to see who have been active recently to find GSoC\n> mentor candidates by running:\n> \n> \t$ git shortlog -s -n --since=4.months | head -n 20\n\nYou aren't alone; I did the same stupid thing last night. Only\nwithout the --since=4.months argument. Which is the old calling\nconvention. At least your little warning would have saved me. ;-)\n\n\nWe need GSoC project mentors!\n\nReading http://git.or.cz/gitwiki/SoC2007Ideas it appears as though\n(with the exception of 2 projects that Martin Langhoff is interested\nin, thanks Martin!) I am *the* GSoC mentor. I really hoped that we\ncould get more community involvement than that. Junio's \"top 20\"\nis an interesting set of people, but there are still some very\ninteresting and qualified names in the top 65...\n\nPlease, look over the SoC2007Ideas list on the wiki and stick your\nname next to a project or two that you have watched on the mailing\nlist, are interested in seeing get added to Git, and would like to\nhelp out with this summer.\n\nBeing a GSoC mentor does have a time commitment. You will need to\nwork with the student via email to help them find their way around\nthe Git source code, and to help them refine their changes such\nthat they are suitable for acceptance to the respective Git tree.\n\nRemember, our goal here is to have a working enhancement that Junio\nwould be proud to merge!\n\n\n-- \nShawn.\n"},{"id":"36631","messageId":"81b0412b0703080804r5e2d933fqabab7306a5f0d6db@mail.gmail.com","threadId":"7150","inReplyTo":"20070308150756.GB30674@spearce.org","subject":"Re: GSoC project mentors","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-03-08T16:04:26Z","receivedAt":"2007-03-08T16:04:26Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"On 3/8/07, Shawn O. Pearce wrote:\n>\n> Being a GSoC mentor does have a time commitment. You will need to\n\nThis is a problem. How about IRC schedules? Say, if some idea\nhas not enough mentorship, it may have at least supporters on\nIRC who _commit_ themselves to that schedule. In this case\nthe students can at least know when they are likely to get help.\n"},{"id":"36634","messageId":"Pine.LNX.4.64.0703080827170.10832@woody.linux-foundation.org","threadId":"7150","inReplyTo":"7vhcsw9h8p.fsf@assigned-by-dhcp.cox.net","subject":"Re: [PATCH] shortlog: prompt when reading from terminal by mistake","fromName":"Linus Torvalds","fromEmail":"torvalds@linux-foundation.org","sentAt":"2007-03-08T16:37:44Z","receivedAt":"2007-03-08T16:37:44Z","isPatch":true,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Thu, 8 Mar 2007, Junio C Hamano wrote:\n> \n> Not so. \"git shortlog\" acts as a filter when no revs are given,\n> unlike \"git log\" which defaults to HEAD. It was reading from\n> its standard input.\n\nCould we just change that?\n\nThere aren't *that* many users of \"git shortlog\", I bet, and I'm not sure \nthe \"filter mode\" is really worth it, especially since it ends up being \nconfusing once you get used to using it as just another \"git log\" variant.\n\nIt was a filter not really because people wanted a filter, but for \nhistorical reasons, and because it wasn't really able to do things on its \nown, and it was just an external script...\n\nYeah, as a filter it *can* stil lbe useful, of course, but I suspect the \nusefullness is limited.\n\n> +\tif (rev.pending.nr == 0) {\n> +\t\tif (isatty(0))\n> +\t\t\tfprintf(stderr, \"(reading log to summarize from standard input)\\n\");\n\nSure, this probably gets some cases (and the one you tried in particular), \nbut if you pipe the output to a pager, I doubt it's actually all that \nuseful.\n\nTo simulate a \"wait a long time without output\" case, try this:\n\n\t( echo \"Important warning\" >&2 ; sleep 10) | less -S\n\nand at least for me, I don't see squat _in_case_I'm_at_the_top_ of the \nwindow, simply because \"less\" will clear the screen for me.\n\nIn other words, putting warnings on stderr usually isn't all that useful \nwhen you have something like a pager that will do tty stuff - it will \neasily overwrite the warning so quickly that you'll never see it at all.\n\nSo I think your patch is an improvement, but I suspect it would be a \nbigger improvement to just make \"git shortlog\" work as \"git log\". If we \nwant to support the filtering mode, we could just make it be a separate \ncommand (\"git shortlog-filter\") instead?\n\n\t\t\tLinus\n"},{"id":"36637","messageId":"Pine.LNX.4.63.0703081755500.22628@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"7150","inReplyTo":"Pine.LNX.4.64.0703080827170.10832@woody.linux-foundation.org","subject":"Re: [PATCH] shortlog: prompt when reading from terminal by mistake","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-03-08T17:10:54Z","receivedAt":"2007-03-08T17:10:54Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 8 Mar 2007, Linus Torvalds wrote:\n\n> On Thu, 8 Mar 2007, Junio C Hamano wrote:\n> > \n> > Not so. \"git shortlog\" acts as a filter when no revs are given, \n> > unlike \"git log\" which defaults to HEAD. It was reading from its \n> > standard input.\n> \n> Could we just change that?\n>\n> [...]\n> \n> Yeah, as a filter it *can* stil lbe useful, of course, but I suspect the \n> usefullness is limited.\n\nHow about something totally different: \"git log --shortlog\". I.e.\n\ndiff --git a/builtin-log.c b/builtin-log.c\nindex 865832c..ad1dafd 100644\n--- a/builtin-log.c\n+++ b/builtin-log.c\n@@ -216,7 +216,11 @@ int cmd_log_reflog(int argc, const char **argv, const char *prefix)\n int cmd_log(int argc, const char **argv, const char *prefix)\n {\n \tstruct rev_info rev;\n+\tint i;\n \n+\tfor (i = 1; i < argc; i++)\n+\t\tif (!strcmp(argv[i], \"--shortlog\"))\n+\t\t\treturn cmd_shortlog(argc, argv, prefix);\n \tgit_config(git_log_config);\n \tinit_revisions(&rev, prefix);\n \trev.always_show_header = 1;\ndiff --git a/builtin-shortlog.c b/builtin-shortlog.c\nindex 29b1636..952a475 100644\n--- a/builtin-shortlog.c\n+++ b/builtin-shortlog.c\n@@ -289,7 +289,7 @@ int cmd_shortlog(int argc, const char **argv, const char *prefix)\n \t\t\tsummary = 1;\n \t\telse if (!strcmp(argv[1], \"-h\") || !strcmp(argv[1], \"--help\"))\n \t\t\tusage(shortlog_usage);\n-\t\telse\n+\t\telse if (strcmp(argv[1], \"--shortlog\"))\n \t\t\tbreak;\n \t\targv++;\n \t\targc--;\n\nCiao,\nDscho\n"},{"id":"36639","messageId":"vpqejnz3b79.fsf@olympe.imag.fr","threadId":"7150","inReplyTo":"Pine.LNX.4.63.0703081755500.22628@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: [PATCH] shortlog: prompt when reading from terminal by mistake","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2007-03-08T17:19:06Z","receivedAt":"2007-03-08T17:19:06Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"Johannes Schindelin writes:\n\n> How about something totally different: \"git log --shortlog\". I.e.\n\nThen, I'd say just --short.\n\n-- \nMatthieu\n"},{"id":"36640","messageId":"Pine.LNX.4.63.0703081826000.22628@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"7150","inReplyTo":"20070308150756.GB30674@spearce.org","subject":"Re: GSoC project mentors","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-03-08T17:27:27Z","receivedAt":"2007-03-08T17:27:27Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 8 Mar 2007, Shawn O. Pearce wrote:\n\n> Please, look over the SoC2007Ideas list on the wiki and stick your name \n> next to a project or two that you have watched on the mailing list, are \n> interested in seeing get added to Git, and would like to help out with \n> this summer.\n\nDone.\n\n> Being a GSoC mentor does have a time commitment. You will need to work \n> with the student via email to help them find their way around the Git \n> source code, and to help them refine their changes such that they are \n> suitable for acceptance to the respective Git tree.\n\nCan't take more time than some of the discussions on the list...\n\n> Remember, our goal here is to have a working enhancement that Junio \n> would be proud to merge!\n\nSpeaking of whom: Junio, if you don't do the backup administrator, I would \nbe willing to.\n\nCiao,\nDscho\n"},{"id":"36641","messageId":"Pine.LNX.4.63.0703081827560.22628@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"7150","inReplyTo":"vpqejnz3b79.fsf@olympe.imag.fr","subject":"Re: [PATCH] shortlog: prompt when reading from terminal by mistake","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-03-08T17:28:12Z","receivedAt":"2007-03-08T17:28:12Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 8 Mar 2007, Matthieu Moy wrote:\n\n> Johannes Schindelin writes:\n> \n> > How about something totally different: \"git log --shortlog\". I.e.\n> \n> Then, I'd say just --short.\n\nToo easy to confuse with \"--pretty=short\".\n\nCiao,\nDscho\n"},{"id":"36643","messageId":"Pine.LNX.4.64.0703080928580.10832@woody.linux-foundation.org","threadId":"7150","inReplyTo":"Pine.LNX.4.63.0703081755500.22628@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: [PATCH] shortlog: prompt when reading from terminal by mistake","fromName":"Linus Torvalds","fromEmail":"torvalds@linux-foundation.org","sentAt":"2007-03-08T17:31:55Z","receivedAt":"2007-03-08T17:31:55Z","isPatch":true,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Thu, 8 Mar 2007, Johannes Schindelin wrote:\n> \n> How about something totally different: \"git log --shortlog\". I.e.\n\nSure, but this is even worse, because the way you wrote the patch, now\n\n\tgit log --shortlog\n\nwill act as a filter too, which is even *more* confusing.\n\nYou also broke something even more fundamental. Try this:\n\n\tgit log -- --shortlog\n\nwith your patch ;)\n\nBut yeah, if \"cmd_shortlog()\" worked like \"git log\" (at least if it sees \nthe \"--shortlog\" flag) and with that obvious filename parsing thing fixed, \nthat thing would be fine.\n\n\t\t\tLinus\n"},{"id":"36645","messageId":"Pine.LNX.4.63.0703081834310.22628@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"7150","inReplyTo":"Pine.LNX.4.64.0703080928580.10832@woody.linux-foundation.org","subject":"Re: [PATCH] shortlog: prompt when reading from terminal by mistake","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-03-08T17:37:05Z","receivedAt":"2007-03-08T17:37:05Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 8 Mar 2007, Linus Torvalds wrote:\n\n> On Thu, 8 Mar 2007, Johannes Schindelin wrote:\n> > \n> > How about something totally different: \"git log --shortlog\". I.e.\n> \n> Sure, but this is even worse, because the way you wrote the patch\n\nI should have marked it as \"this is the idea, but even if it looks like a \npatch, it is not\".\n\nUnfortunately, I don't have time to do a proper patch, which is why I just \nwrote that simple and completely untested example of how this could be \ndone.\n\nI'd split off a proper builtin_shortlog(revs) from cmd_shortlog(), to \navoid double parsing, and also because it looks nicer to the eye, but time \nis scarce.\n\nCiao,\nDscho\n"},{"id":"36656","messageId":"20070309005940.GA32211@spearce.org","threadId":"7150","inReplyTo":"81b0412b0703080804r5e2d933fqabab7306a5f0d6db@mail.gmail.com","subject":"Re: GSoC project mentors","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-03-09T00:59:40Z","receivedAt":"2007-03-09T00:59:40Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Alex Riesen wrote:\n> On 3/8/07, Shawn O. Pearce wrote:\n> >\n> >Being a GSoC mentor does have a time commitment. You will need to\n> \n> This is a problem. How about IRC schedules? Say, if some idea\n> has not enough mentorship, it may have at least supporters on\n> IRC who _commit_ themselves to that schedule. In this case\n> the students can at least know when they are likely to get help.\n\nCommitting oneself to being on IRC is a time commitment, isn't it?\n:-)\n\nIRC time is difficult for me; I do hang out there more often than\nI used to now that the community is doing the same, but I spend\na good part of my week working from a network where IRC access\nisn't allowed.\n\nAnyway, people did step up (thanks Pasky, Dscho, Brian, Martin,\nMartin!) and now most projects have more one mentor. This is\nexactly what I was hoping would happen.\n\n-- \nShawn.\n"},{"id":"36658","messageId":"20070309022616.GD32211@spearce.org","threadId":"7150","inReplyTo":"Pine.LNX.4.63.0703081826000.22628@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: GSoC project mentors","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-03-09T02:26:16Z","receivedAt":"2007-03-09T02:26:16Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Johannes Schindelin wrote:\n> Speaking of whom: Junio, if you don't do the backup administrator, I would \n> be willing to.\n\nMartin Langhoff agreed first, so that is who I listed. I think he\nis also listed as mentor for fewer projects than you are. ;-)\n\n-- \nShawn.\n"},{"id":"36669","messageId":"81b0412b0703090150r674e754bn921d86eb40563e2a@mail.gmail.com","threadId":"7150","inReplyTo":"20070309005940.GA32211@spearce.org","subject":"Re: GSoC project mentors","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-03-09T09:50:16Z","receivedAt":"2007-03-09T09:50:16Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"On 3/9/07, Shawn O. Pearce wrote:\n> Alex Riesen wrote:\n> > On 3/8/07, Shawn O. Pearce wrote:\n> > >\n> > >Being a GSoC mentor does have a time commitment. You will need to\n> >\n> > This is a problem. How about IRC schedules? Say, if some idea\n> > has not enough mentorship, it may have at least supporters on\n> > IRC who _commit_ themselves to that schedule. In this case\n> > the students can at least know when they are likely to get help.\n>\n> Committing oneself to being on IRC is a time commitment, isn't it?\n> :-)\n\nyes, but it is a smaller one. And the suggestion was to commit to specific\ndate and time.\n\n> IRC time is difficult for me; I do hang out there more often than\n> I used to now that the community is doing the same, but I spend\n> a good part of my week working from a network where IRC access\n> isn't allowed.\n\nMe too. But I would gladly spent some time on IRC when I'm home,\nwhich usually is after 20:00 CET. Especially if I promised to.\n"},{"id":"36675","messageId":"esrrh3$rmb$1@sea.gmane.org","threadId":"7150","inReplyTo":"Pine.LNX.4.63.0703081755500.22628@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: [PATCH] shortlog: prompt when reading from terminal by mistake","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2007-03-09T14:41:02Z","receivedAt":"2007-03-09T14:41:02Z","isPatch":true,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Johannes Schindelin wrote:\n\n> On Thu, 8 Mar 2007, Linus Torvalds wrote:\n> \n>> On Thu, 8 Mar 2007, Junio C Hamano wrote:\n>>> \n>>> Not so. \"git shortlog\" acts as a filter when no revs are given, \n>>> unlike \"git log\" which defaults to HEAD. It was reading from its \n>>> standard input.\n>> \n>> Could we just change that?\n>>\n>> [...]\n>> \n>> Yeah, as a filter it *can* stil lbe useful, of course, but I suspect the \n>> usefullness is limited.\n> \n> How about something totally different: \"git log --shortlog\". I.e.\n\nOr have old filter behavior only with \"git shortlog --stdin\" option?\nPerhaps in git 1.5.1...\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"},{"id":"36680","messageId":"20070309155822.GB1131@spearce.org","threadId":"7150","inReplyTo":"81b0412b0703090150r674e754bn921d86eb40563e2a@mail.gmail.com","subject":"Re: GSoC project mentors","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-03-09T15:58:22Z","receivedAt":"2007-03-09T15:58:22Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Alex Riesen wrote:\n> On 3/9/07, Shawn O. Pearce wrote:\n> >Committing oneself to being on IRC is a time commitment, isn't it?\n> >:-)\n> \n> yes, but it is a smaller one. And the suggestion was to commit to specific\n> date and time.\n> \n> >IRC time is difficult for me; I do hang out there more often than\n> >I used to now that the community is doing the same, but I spend\n> >a good part of my week working from a network where IRC access\n> >isn't allowed.\n> \n> Me too. But I would gladly spent some time on IRC when I'm home,\n> which usually is after 20:00 CET. Especially if I promised to.\n\nLooking at the way other successful projects have worked with GSoC,\nit seems to really pay to have a couple of mentors per student.\nThe students don't always reach out to the mailing list right away\nwhen they don't understand something or are seeking feedback on\nan approach, as they might be shy or might be afraid of getting\nflamed by one of the \"old hands\". This is where having accessible\nmentors comes in nicely, as the mentor can help the student frame\ntheir message and get it into the public forum. Likewise having\nmore than one mentor gives the student somewhere to turn when one\nof the mentors takes a week of vacation.\n\nMost of our projects do have more than one mentor listed now (thanks\nguys!). As our group's coordinator I intend on trying to make sure\nevery project has at least two mentors assigned to it and actively\nparticipating with the student. But given the way our community\nworks, I fully expect the whole community to be involved as patches\nare posted and discussed on the mailing list. Students need to be\ninteracting with all of us on git@vger, not just their mentors.\n\nHaving a fairly consistent presence on IRC would also be good.\nI'm not quite sure yet how I'm personally going to do that this\nsummer scheduling wise, but I think it would be good if we can\nhave a few individuals on #git on a regularly scheduled basis.\nI'd love to see you there, along with some of our other regulars.\n\n-- \nShawn.\n"},{"id":"36704","messageId":"7vwt1q2apf.fsf@assigned-by-dhcp.cox.net","threadId":"7150","inReplyTo":"Pine.LNX.4.64.0703080827170.10832@woody.linux-foundation.org","subject":"Re: [PATCH] shortlog: prompt when reading from terminal by mistake","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-03-10T00:39:40Z","receivedAt":"2007-03-10T00:39:40Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Linus Torvalds writes:\n\n> Sure, this probably gets some cases (and the one you tried in particular), \n> but if you pipe the output to a pager, I doubt it's actually all that \n> useful.\n>\n> To simulate a \"wait a long time without output\" case, try this:\n>\n> \t( echo \"Important warning\" >&2 ; sleep 10) | less -S\n>\n> and at least for me, I don't see squat _in_case_I'm_at_the_top_ of the \n> window, simply because \"less\" will clear the screen for me.\n\n> In other words, putting warnings on stderr usually isn't all that useful \n> when you have something like a pager that will do tty stuff - it will \n> easily overwrite the warning so quickly that you'll never see it at all.\n\nThat is correct in general, but you are being unfair.\n\nYou know git-shortlog has built-in pager _and_ you know _you_\nadded select(2) before spawning less, so that when that warning\nis emitted, less hasn't even started running --- it cannot clear\nthe display.\n"}]}