This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Getting patches out of HTML archives (was Re: EGCS web pages)
>>>>> "Jason" == Jason Molenda <jsm@cygnus.com> writes:
Jason> However, the one benefit that we gained by not HTML'ifying
Jason> code is that no matter how the user saves the file, they
Jason> can run patch on it. e.g. they can save it as "Source"
Jason> (HTML), and patch will work. Or they can save it as "Plain
Jason> text" and have a good chance of it working correctly.
That's what I meant. I said `cut-and-paste' as a shorthand, but
`save-as-source' is what I really do.
Jason> I'll have to think about this some more, but by default I'm
Jason> going to be HTMLifying the messages if I can apply patches
Jason> successfully once they've been saved as Plain text from a
Jason> browser.
That's a fine criterion. You might try checking out a few old
versions of EGCS, and finding some big patches from the egcs-patches
archives for some `real-word' tests. But, in any case, it sounds like
you've got the issues squarely in mind; thanks for helping out with
this all around.
--
Mark Mitchell mark@markmitchell.com
Mark Mitchell Consulting http://www.markmitchell.com