Hi Chuck, Ralf, Den 2010-09-05 22:49 skrev Charles Wilson: > [meta-request: in the future, could you not use whatever option it is > that causes the entire patch message to be stored at attachment to the > actual message...this is a little awkward to reply-to:] > > On 9/5/2010 3:58 PM, Peter Rosin wrote: > <nothing> > > ...which means all replies have to manually cut-n-paste-as-quotation > which is painful. Unless somebody knows what option to set in TBird to > DTRT?
If *I* inline the patches, TBird messes up tabs -> four spaces, haven't found a way to avoid that... I *could* use mutt for sending patches I suppose, but isn't the attachment marked to be inline? I think they were when I tested my current patch sending technique... *looks* No, "Content-Disposition: attachment;" #...@$&#%& > On 9/5/2010 3:58 PM, Peter Rosin wrote: >> +...@defvar to_tool_file_cmd > > Urk. I guess I ought to go ahead and define to_host_file_cmd... > > You might also want to add a line or two to the new section concerning > the "lying" cygwin->mingw case: > >> ...To force the >> correct file name conversion in this situation, you should do the >> following _before_ running configure: >> >> export lt_cv_to_host_file_cmd=func_convert_file_cygwin_to_w32 > > ...Unless you plan to do all of that as part of some other pure-doc patch. I have a patch ready with some updates to both the fake and the lying case (and the nits requested by Ralf), will see if I can find a way to post without destroying tabs and without causing you all trouble... Also, no comments for 2/7 and 3/7, does that mean that those are ok? Cheers, Peter