My comments below... On Sat, Jan 26, 2013 at 6:55 PM, Phani Bhushan Tholeti <[email protected]>wrote:
> > > > On Sat, Jan 26, 2013 at 8:44 PM, Nalin Savara <[email protected]> wrote: > >> >> >> On Sat, Jan 26, 2013 at 5:06 PM, Shantanu Gupta <[email protected]>wrote: >> >>> On Sat, Jan 26, 2013 at 4:10 PM, Nalin Savara <[email protected]> wrote: >>> >>>> >>>> >>>> On Sat, Jan 26, 2013 at 3:22 PM, ragsagar <[email protected]> wrote: >>>> >>>>> On Sat, Jan 26, 2013 at 3:07 PM, Nalin Savara <[email protected]>wrote: >>>>> >>>>>> Hi People... >>>>>> >>>>>> <snip> >>>> >>>> Thanks a ton ragsagar... that truely helps. >>>> >>> > This seems to be worse than top posting ;) > Nothing here helps... > > >> >>> Please don't "snip" responses/suggestions/solutions when you reply to a >>> mailing list unless you have an appalling reason to do so. >>> >> >> Buddy... Shantanu... reason for snipping is same as reason for not >> top-posting-- >> > > But when you send the same mail to many people/lists, and get a reply from > one list, the other lists don't get to know what the reply is/was. Like it > was in this case > My friend Phani-- in this case-- the answerer did a reply-all-- hence all lists I asked originally got a cc: of the message. And. if you hate top posting so much, better do inline posting. Its much > context aware. > > >> that people getting dozens of messages in a digest find it impossible to >> manage them because of large content size and repititions. >> >> Will therefore continue. >> >> Also, "apalling"-- means "horrifying"-- hence not sure what you meant >> when you said: "unless you have a apalling reason...". >> > > And since we seem to be getting pedantic, its "appalling" not "apalling". > And its not just "horrifying" but also to appall is also to dismay > thanks for the gyan bro!!! Mucho appreciato ;-) > > > -- > Lots o' Luv, > Take it easy... -Nalin -- -- Mailing list guidelines and other related articles: http://lug-iitd.org/Footer
