imread

[Ben Abbott]

On Tuesday, July 15, 2008, at 02:42PM, "Thomas L. Scofield" <scofield at calvin.edu> wrote:
>
>On Jul 14, 2008, at 4:14 PM, John W. Eaton wrote:
>
>> On 12-Jul-2008, Thomas L. Scofield wrote:
>>
>> | I hope this is what is needed.  I'm sending two changesets (or
>> | whatever is produced by "export tip"), lamely giving them the
>> | extension .changeset.  (I'm not sure what the usual extension is.  I
>> | think I sometimes see .ksh files in the archives.)
>>
>> I don't care what you call the file, but it is slightly easier for me
>> if you send text/plain attachments instead of binary attachments.
>>
>
>I'm not exactly sure what to do differently.  The files on my machine  
>are text files.  I included them as attachments (email program is the  
>Mac Mail program).  At what stage would they have become binary files?
>
>

I'm also a Mac user, and encountered the same (at least very similar) problem in the past.

In my case, there were two causes.

(1) The files were RTF files (which was the default in my Mail Preferences). You can force TextEdit or Mail to convert to plain text, and can change the preferences for Mail so that it sends plain text.

(2) In addition, the EOL character was occasionally wrong. For than I used a mac2unix command line utility.

To avoid each of these problems, I eventually used unix style redirection to save the chageset directly to a file (from the Terminal) and then attached the saved changeset to the email. For example,

hg export tip > ~/Desktop/myChangeSet.diff

Ben