Hi Peff,
On Thu, 3 Nov 2016, Jeff King wrote:
> On Thu, Nov 03, 2016 at 11:34:53AM -0400, Jeff King wrote:
>
> > This is missing a Content-Transfer-Encoding. I think the default is the
> > traditional 7-bit ascii encoding, but your body has characters with the
> > high-bit set (your UTF-8 bullet
On Thu, Nov 03, 2016 at 11:38:45AM -0400, Jeff King wrote:
> On Thu, Nov 03, 2016 at 11:34:53AM -0400, Jeff King wrote:
>
> > This is missing a Content-Transfer-Encoding. I think the default is the
> > traditional 7-bit ascii encoding, but your body has characters with the
> > high-bit set (your
On Thu, Nov 03, 2016 at 11:34:53AM -0400, Jeff King wrote:
> This is missing a Content-Transfer-Encoding. I think the default is the
> traditional 7-bit ascii encoding, but your body has characters with the
> high-bit set (your UTF-8 bullet).
>
> Try adding:
>
> Content-Transfer-Encoding: 8bit
es Schindelin
> Date: Wed, 02 Nov 2016 21:43:54 +0100
> To: git-for-wind...@googlegroups.com, git@vger.kernel.org
> Subject: [ANNOUNCE] Git for Windows 2.10.2
> Content-Type: text/plain; charset=UTF-8
> Fcc: Sent
> -- snap --
This is missing a Content-Transfer-Encoding. I
the very first time, and the headers of the mbox file I
> fed to that command read thusly:
>
> -- snip --
> From 2.10.2.windows.1 Mon Sep 17 00:00:00 2001
> From: Johannes Schindelin
> Date: Wed, 02 Nov 2016 21:43:54 +0100
> To: git-for-wind...@googlegroups.com, git@vger.kerne
nip --
From 2.10.2.windows.1 Mon Sep 17 00:00:00 2001
From: Johannes Schindelin
Date: Wed, 02 Nov 2016 21:43:54 +0100
To: git-for-wind...@googlegroups.com, git@vger.kernel.org
Subject: [ANNOUNCE] Git for Windows 2.10.2
Content-Type: text/plain; charset=UTF-8
Fcc: Sent
-- snap --
The only problem
Dear Git users,
It is my pleasure to announce that Git for Windows 2.10.2 is available from:
https://git-for-windows.github.io/
Changes since Git for Windows v2.10.1(2) (October 13th 2016)
Git for windows v2.10.1(2) was a MinGit-only release (i.e. there was no
Git for windows installer
7 matches
Mail list logo