On Tue, Aug 25, 2009 at 5:35 PM, Jakub Narebski<jnareb@xxxxxxxxx> wrote: > Sitaram Chamarty wrote: >> On Tue, Aug 25, 2009 at 12:14 AM, Jakub Narebski<jnareb@xxxxxxxxx> wrote: >> > Wouldn't it be better to use "use warnings" instead of 'perl -w'? >> I'm not sure what is the minimum perl required for git > I think that git requires Perl at least version 5.6 thanks; I'll change "-w" to "use warnings" >> > It would be, I think, better if you have used POD for such >> > documentation. One would be able to generate manpage using pod2man, >> > and it is no less readable in source code. See e.g. perl/Git.pm or >> > contrib/hooks/update-paranoid. >> >> Hmm... I've been spoiled by Markdown's sane bullet list >> handling. Visually, POD forces everything other than code >> to be flush left -- any sort of list is definitely less >> readable in source code as a result. IMHO of course. > > How it is relevant to the issue at hand? I was talking about replacing > documentation comments in the header with POD markup. > > Also you usually document top-level structures with POD. Forget I mentioned markdown :) All I'm saying is that even in the documentation you speak of, I have a couple of small "lists". And I like lists to be properly indented, that's all -- I am mentally unable to edit them if they are all flush left :-( just like it's irritating to edit code that's mis-indented or not indented. Sorry...! And yes, one of my python friends has then asked "why do you not like python". I have no answer. As Whitman said (http://www.quotationspage.com/quote/26914.html): Do I contradict myself? Very well then I contradict myself, (I am large, I contain multitudes.) :-) Regards, -- Sitaram "not normally given to quoting poets" Chamarty -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html