{"thread":{"id":"43420","subject":"Re: [PATCH] gitweb: Show project's README.html if available","startedAt":"2006-10-24T19:09:03Z","lastAt":"2006-10-24T19:50:35Z","messageCount":4,"participants":["Luben Tuikov","Petr Baudis"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"296667","messageId":"524029.7339.qm@web31812.mail.mud.yahoo.com","threadId":"43420","inReplyTo":"20061024113057.GA20017@pasky.or.cz","subject":"Re: [PATCH] gitweb: Show project's README.html if available","fromName":"Luben Tuikov","fromEmail":"ltuikov@yahoo.com","sentAt":"2006-10-24T19:09:03Z","receivedAt":"2006-10-24T19:09:03Z","isPatch":true,"sender":{"key":"ltuikov@yahoo.com","avatar":null},"body":"--- Petr Baudis <pasky@suse.cz> wrote:\n> > Why not instead re-submit a patch implementing what was discussed\n> > in this thread bearing the same name:\n> > \n> > http://marc.theaimsgroup.com/?t=116044914900001&r=1&w=2\n> \n> This implements\n> \n> \thttp://marc.theaimsgroup.com/?l=git&m=116047939517299&w=2\n> \n> I see no other ideas I could take there except various naming proposals\n> and perhaps using File::Copy but I'll wait until someone does a\n> gitweb-wide change for the latter.\n> \n> I don't really care _what_ name it bears, but I'd like to have it\n> included. :-)\n\nPeople have suggested that this functionality be folded into the\n\"Description\" column, where the description printed is the\nfirst line of the description file \"description\" and if clicked\non, it shows the whole \"descrption\" file.\n\n    Luben\n"},{"id":"295498","messageId":"20061024191915.GV18879@pasky.or.cz","threadId":"43420","inReplyTo":"524029.7339.qm@web31812.mail.mud.yahoo.com","subject":"Re: [PATCH] gitweb: Show project's README.html if available","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2006-10-24T19:19:15Z","receivedAt":"2006-10-24T19:19:15Z","isPatch":true,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"On Tue, Oct 24, 2006 at 09:09:03PM CEST, Luben Tuikov wrote:\n> --- Petr Baudis <pasky@suse.cz> wrote:\n> > > Why not instead re-submit a patch implementing what was discussed\n> > > in this thread bearing the same name:\n> > > \n> > > http://marc.theaimsgroup.com/?t=116044914900001&r=1&w=2\n> > \n> > This implements\n> > \n> > \thttp://marc.theaimsgroup.com/?l=git&m=116047939517299&w=2\n> > \n> > I see no other ideas I could take there except various naming proposals\n> > and perhaps using File::Copy but I'll wait until someone does a\n> > gitweb-wide change for the latter.\n> > \n> > I don't really care _what_ name it bears, but I'd like to have it\n> > included. :-)\n> \n> People have suggested that this functionality be folded into the\n> \"Description\" column, where the description printed is the\n> first line of the description file \"description\" and if clicked\n> on, it shows the whole \"descrption\" file.\n\nPlease look at the mail the mail I referred was a reply to:\n\n\thttp://marc.theaimsgroup.com/?l=git&m=116047773825208&w=2\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\n#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj\n$/=unpack('H*',$_);$_=`echo 16dio\\U$k\"SK$/SM$n\\EsN0p[lN*1\n"},{"id":"294694","messageId":"701637.67420.qm@web31802.mail.mud.yahoo.com","threadId":"43420","inReplyTo":"20061024191915.GV18879@pasky.or.cz","subject":"Re: [PATCH] gitweb: Show project's README.html if available","fromName":"Luben Tuikov","fromEmail":"ltuikov@yahoo.com","sentAt":"2006-10-24T19:41:04Z","receivedAt":"2006-10-24T19:41:04Z","isPatch":true,"sender":{"key":"ltuikov@yahoo.com","avatar":null},"body":"--- Petr Baudis <pasky@suse.cz> wrote:\n> On Tue, Oct 24, 2006 at 09:09:03PM CEST, Luben Tuikov wrote:\n> > --- Petr Baudis <pasky@suse.cz> wrote:\n> > > > Why not instead re-submit a patch implementing what was discussed\n> > > > in this thread bearing the same name:\n> > > > \n> > > > http://marc.theaimsgroup.com/?t=116044914900001&r=1&w=2\n> > > \n> > > This implements\n> > > \n> > > \thttp://marc.theaimsgroup.com/?l=git&m=116047939517299&w=2\n> > > \n> > > I see no other ideas I could take there except various naming proposals\n> > > and perhaps using File::Copy but I'll wait until someone does a\n> > > gitweb-wide change for the latter.\n> > > \n> > > I don't really care _what_ name it bears, but I'd like to have it\n> > > included. :-)\n> > \n> > People have suggested that this functionality be folded into the\n> > \"Description\" column, where the description printed is the\n> > first line of the description file \"description\" and if clicked\n> > on, it shows the whole \"descrption\" file.\n> \n> Please look at the mail the mail I referred was a reply to:\n> \n> \thttp://marc.theaimsgroup.com/?l=git&m=116047773825208&w=2\n\nI re-read that email.  And I also saw what you have at hed.git.\n\nIf anything I think we should want to _minimize_ shown material\nbefore the \"shortlog\" in the \"summary\" page.\n\nWhy?\n\nWell, in a production environment, people often view the \"summary\" page\nto see what has been going on with a project and they are well aware\nof what that project is for and/or what it does.  It is cumbersome to have\nto scroll down each and every time past he annoying \"readme\", just to see\nthe first few commits.\n\nLook, your hed.cgi has 7 lines for the description and URL, (as opposed to 4\nof next:gitweb.perl) and those already have generous amount of inner-spacing,\nmaking the whole thing extend half the page.  This would be annoying in\na production environment.\n\nNow, if you use gitweb as a Web presentation tool of your projects then\nthis is another story.  Then you would want to put colors, graphics, lots\nof text here and there, etc, etc.\n\nIf we start to include those little things to be supported \"optionally\",\nthen we incur bloat to gitweb.\n\nI think what is best to do is to create another script which can show\nthe fancy-schmancy Web presentation content you want to mix with\nwith gitweb, and keep gitweb a tool for the enigineer as opposed to\na web presentation application.\n\nThat other fancy-schmancy script can keep track of developers,\nstatistics, bugs, bug counts, etc, etc, as well.\n\n    Luben\n"},{"id":"297537","messageId":"20061024195035.GH20017@pasky.or.cz","threadId":"43420","inReplyTo":"701637.67420.qm@web31802.mail.mud.yahoo.com","subject":"Re: [PATCH] gitweb: Show project's README.html if available","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2006-10-24T19:50:35Z","receivedAt":"2006-10-24T19:50:35Z","isPatch":true,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Tue, Oct 24, 2006 at 09:41:04PM CEST, I got a letter\nwhere Luben Tuikov <ltuikov@yahoo.com> said that...\n> I re-read that email.  And I also saw what you have at hed.git.\n> \n> If anything I think we should want to _minimize_ shown material\n> before the \"shortlog\" in the \"summary\" page.\n> \n> Why?\n> \n> Well, in a production environment, people often view the \"summary\" page\n> to see what has been going on with a project and they are well aware\n> of what that project is for and/or what it does.  It is cumbersome to have\n> to scroll down each and every time past he annoying \"readme\", just to see\n> the first few commits.\n\nYes, I agree that this is valid concern. I've been thinking about\nshowing readme in parallel with the summary box, do people think that\nwould fix the issue?\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\n#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj\n$/=unpack('H*',$_);$_=`echo 16dio\\U$k\"SK$/SM$n\\EsN0p[lN*1\n"}]}