On Sat, 6 Sep 1997 jmknoble_at_pobox.com wrote:
> Actually, the above isn't line wrap; the part i underlined above is the
> beginning of the next `hunk' (to use patch's terminology), and the
> single asterisk is actually supposed to be that way.
>
> However, Adam's concern is somewhat valid, especially for longer
> patches. Best thing to do is to use a MIME attachment if you can. For
> shorter patches, i'd just give it a once-over to check for long lines
> that might wrap.
I thought it was agreed to a while ago that patches (or anything sizable
for that matter) should not be attached, inlined, or anything... They
should be placed on an FTP server to be requested when someone would
actually want it, thereby reducing people getting pissed off by 20k gif's
in their inboxes or 200k binaries, etc...
-peace
--- BEGIN GEEK CODE BLOCK ------------+-----------
GAT d- s:+ !a C+(+++) UI/L/S/B++(+++) | "In the morning glad I see
P>+ L+(++) E---- W+++ N+ o? K? w++++ | My foe outstrech'd beneath the tree."
O--- M-- V PS+++_at_ PE Y-- PGP+ t++ 5 | -The Poison Tree
X++ R- tv+ b DI++ D+ G e>* h*(!) r- | William Blake
y*(+) ------ END GEEK CODE BLOCK -----+
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Sat Sep 06 1997 - 11:18:27 BST