I disagree. Most modern e-mail clients and webmail (gmail for example) will colapse the 'cruft'. Further, when I come apon a discussion that I found through searching the web.. I'd much rather hage the entire conversation there, rather then have to find the start of the thread and then keep clicking through it to read it. It's much easier to just go to the bottom and read back through the entire dialog. <div>On 3/12/07, Daniel Bodanske <<a href="mailto:daengbo@gmail.com">daengbo@gmail.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Top posting is normally bad because the cruft at the bottom doesn't get edited / deleted (just like I did here as an illustration), even though it's not needed or wanted anymore. Dan On 3/12/07, Nils Breunese < <a href="mailto:nils@breun.nl">nils@breun.nl</a>> wrote: > Sudev Barar wrote: > > > Thanks Joe, This is exact type of information I needed to bring in > > some list discipline. I know many people may not like it, just like > > frowns on inline and bottom posting requests. > > A: Because it disrupts the proper flow of reading. > Q: Why is top posting bad? > > Nils. > > _______________________________________________ > K12OSN mailing list > <a href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a> > <a href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a> > For more info see < <a href="http://www.k12os.org">http://www.k12os.org</a>> > > _______________________________________________ K12OSN mailing list <a href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/k12osn"> https://www.redhat.com/mailman/listinfo/k12osn</a> For more info see <<a href="http://www.k12os.org">http://www.k12os.org</a>> </blockquote></div>