From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-33761-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 16901 invoked by alias); 22 Nov 2014 22:35:17 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 33761
Received: (qmail 7073 invoked from network); 22 Nov 2014 22:35:16 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
	autolearn=ham version=3.3.2
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.1 cv=AKpDk7pY c=1 sm=1 tr=0	a=FT8er97JFeGWzr5TCOCO5w==:117
 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8	a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10
 a=5y4faFyK3SkA:10	a=JrLlJU6daF65i2p6Vo8A:9 a=CjuIK1q_8ugA:10 a=fFIeaD-CkM4A:10
	a=Oax8oV7wYngA:10 a=QVVAL5tAcasA:10
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <141122143508.ZM15626@torch.brasslantern.com>
Date: Sat, 22 Nov 2014 14:35:08 -0800
In-reply-to: <5470BE8D.5030009@eastlink.ca>
Comments: In reply to Ray Andrews <rayandrews@eastlink.ca>
 "Re: trouble with debugging binary" (Nov 22,  8:49am)
References: <930.1416260160@thecus.kiddle.eu>
	<42F4E5F2-97E7-4803-87CB-B1C67CD943B2@kba.biglobe.ne.jp>
	<15511.1416528068@thecus.kiddle.eu>	<546E9224.7090709@eastlink.ca>
	<CAHYJk3Tca_aAn5mjtGb24DDeor28Jk+M9aBYLQhC__Y5-BubUQ@mail.gmail.com>
	<546EA58F.7010101@eastlink.ca>	<141120222353.ZM10495@torch.brasslantern.com>
	<546F7646.7080108@eastlink.ca>	<141121204545.ZM11623@torch.brasslantern.com>
	<141121214351.ZM12585@torch.brasslantern.com>	<5470BE8D.5030009@eastlink.ca>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: trouble with debugging binary
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On Nov 22,  8:49am, Ray Andrews wrote:
} Subject: Re: trouble with debugging binary
}
} These patches, they don't look like normal diffs, is it a git
} exclusive? Are they applied by some git subcommand?

They're just "git diff" output, I hadn't notice them being something
that couldn't be fed to "patch" but AFAIK there is no magic git way
to apply them.  However, I've already pushed this one so you should
be able to "git pull" it.