X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=v6EkMGNX6w0kzbA8XNLhcTys8GufE8pv9TJOypvnTFBdAZnG1JZAX
	53xEZzWVTEUStaFSVryKh7UtJRqjiN1o+HB8rrjXVi+FlxuVRm+Y+Ss8lIsphhP5
	mOYp1uxM6t0yeJJxVVjkOAYBFcomEafPOapxxFJ098N+59VC0YZca4=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=+xRNyw8r9Ac73FzkzIyL0sVw4Sg=; b=IgsnsIx2+lg0HmsApViOyKoyOnSx
	DFLAKx5MzCp0lEnE91Ut+lJIWHNvd1Iwy5uvJfbLIxmetszcNxZNT4BviOBWCdaz
	FXrVKkDCdQvFaWtgHm4AkrUNpytbXQ7R3XqTUMU2CailC5unC09Dco/P0W7CJF/F
	SAEBW7h9kYaqkHE=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-101.9 required=5.0 tests=AWL,BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=H*c:application, respond
X-HELO:	drew.franken.de
Date:	Wed, 7 Jun 2017 20:56:31 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Installing sshd on W7 reveals errors in CSIH_SCRIPT -- patch file against master
Message-ID:	<20170607185631.GD13513@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<c50589c74b974315dd7756109e270c74 AT xs4all DOT nl> <a2907cfe582879ff35f5357cf937c279 AT xs4all DOT nl> <20170607091501 DOT GB5971 AT calimero DOT vinschen DOT de> <e254a19b71087a19d79291df5ca33b2e AT smtp-cloud2 DOT xs4all DOT net> <20170607143557 DOT GA13513 AT calimero DOT vinschen DOT de> <27a350876c16a8f0c070764fc37b2000 AT smtp-cloud2 DOT xs4all DOT net>
MIME-Version:	1.0
In-Reply-To:	<27a350876c16a8f0c070764fc37b2000@smtp-cloud2.xs4all.net>
User-Agent:	Mutt/1.8.0 (2017-02-23)

--yVhtmJPUSI46BTXb
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jun  7 20:17, Houder wrote:
> On Wed, 7 Jun 2017 16:35:57, Corinna Vinschen wrote:
>=20
> [snip]
> > > Sigh! ... it has been years and YEARS! since I exercised git. So I at=
temp=3D
> > ted
> > > to do what you are asking for ...
> > >=3D20
> > >  - cloned csih
> > >  - branched
> > >  - created TWO fixes in that branch
> > >  - invoked 'git format-patch -n HEAD^^' # which is completely new to
> > >=3D20
> > > Two files were created ... I included them here. Sufficient?
> >=20
> > Well, this is pretty awkward.  I have to extract the patches from the
> > mail and apply them then.  It's easier to have them as *real* attachmen=
ts,
> > or just sent as patch series by `git send-email'C, so they apply without
> > having to edit them.
>=20
> Sorry ...
>=20
> My regular MUA does not support 'In-Reply-to' ...
>=20
> Therefore I cannot use my regular MUA, as I am NOT subcribed to the list;=
 for
> this reason, I make use of a kludge, which allows me to respond to the th=
read.

`git send-email' creates the correct information automatically and it
doesn't use your MUA at all, so that's the easiest way to send patches
to a list, usually.

> However this kludge does not support sending attachments.
>=20
> Next time I will do both. Respond to the thread with a reply that will re=
fer
> to a message (sent by my regular MUA) which will have the attachements.
>=20
> Would that fullfil all requirements?

It's not about "requirements" per se, it's just about making the stuff
easy for the typical, lazy maintainer ;)


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--yVhtmJPUSI46BTXb
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJZOExfAAoJEPU2Bp2uRE+gsbYP/isZMwvPYed0lQmvtp+fWC2i
calmKK6F1DtPuu2sQdx36MvcWGd9JVKvUadSbk2ydPv+VytRjlu0O9KyhLo1Zc/X
TLLKBQAkIXnVcHV+R7xNKLPgcESmfM2cR8K4y+O+ocBITWN0Qx8tIDw73eFs0Qej
cQ4hf9tCs9K0drOJnzO5QWbMyv8BytHBej7PVPcUAv9BIM9aPsGUoWMOgL40cUNj
1jyS1Pxxz6W8tloowVlYDQU4DnurvRCB+SCS7VW7DEfU4J6w4bKuXMp/3gtMONa3
72mGMW0qW8uNDm7RwBAokoBs5FBx97+n20kvPioOfzzM7hoVNdFipnyUS7BENc/q
22LXfTOmoi6Wx7IcEuxKm+vpJuoz0B8N6PrgzoTfS8eQdGZd0XB2UUEp5Lroh6JB
QGB9d6DPforK/dUkybXEYjbKXdZdGRnbmz1R4qF18r80UgDBFoh8WwZ8i+Gyt0nZ
qlp0qZK+j9rf3rW1OTj9herLriiZpfKRjbPDK91C4uvpH2/xgumfIL+noF4ixrt6
qDVYTNFWEzdx+m0NNGjbeZuGPHhYrk/c53l6ZMlouIGldtFjxRsKlCDqWH1/c8+g
uOHAZotrYFYhi5/suB8xLCe76zObZa4iYU9rayapLV700rlRgrlgWd4RbJ8hs4SS
rKyK4DQvqT34OsGQzSV9
=Yn+G
-----END PGP SIGNATURE-----

--yVhtmJPUSI46BTXb--

- Raw text -