--- On Sun, 28/2/10, Andrew Eikum wrote:
> I'd be very surprised if git is modifying your patches
> without telling you. It's probably Gmail trying to be
> clever. Telling git-imap-send to send as an attachment
> (--attach) might fix the issue. Or, if you're already
> doing that, maybe turning
On Sun, Feb 28, 2010 at 3:16 PM, Andrew Eikum
wrote:
> I'd be very surprised if git is modifying your patches without telling you.
> It's probably Gmail trying to be clever. Telling git-imap-send to send as
> an attachment (--attach) might fix the issue. Or, if you're already doing
> that, mayb
On 02/28/2010 02:01 PM, Dylan Smith wrote:
I have been using git imap-send to upload the patch from gmail's draft
folder so that I could send manually after looking over everything,
but all the text piped into git imap-send has unix line endings. I am
not sure if gmail is changing the line endin
On Sun, Feb 28, 2010 at 1:09 PM, James McKenzie
wrote:
>
> git apply complains about whitespace errors:
> 0001-richedit-Documented-paragraph-border-widths-are-in-p.patch:10:
> trailing whitespace.
> int ME_GetParaBorderWidth(ME_Context *c, int flags);
> 0001-richedit-Documented-paragraph-border-wi
Dylan Smith wrote:
> The border widths documented by msdn are in points which are 72 dpi, which
> is not equivalent to pixels (normally 96 dpi). I pre-converted all the
> border widths to 96 dpi resolution since this avoids needed to store
> fractions, and often avoids the need for convertion to th
