From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Installing sshd on W7 reveals errors in CSIH_SCRIPT -- patch file against master
Date: Wed, 07 Jun 2017 18:56:00 -0000 [thread overview]
Message-ID: <20170607185631.GD13513@calimero.vinschen.de> (raw)
In-Reply-To: <27a350876c16a8f0c070764fc37b2000@smtp-cloud2.xs4all.net>
[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]
On Jun 7 20:17, Houder wrote:
> On Wed, 7 Jun 2017 16:35:57, Corinna Vinschen wrote:
>
> [snip]
> > > Sigh! ... it has been years and YEARS! since I exercised git. So I attemp=
> > ted
> > > to do what you are asking for ...
> > >=20
> > > - cloned csih
> > > - branched
> > > - created TWO fixes in that branch
> > > - invoked 'git format-patch -n HEAD^^' # which is completely new to
> > >=20
> > > Two files were created ... I included them here. Sufficient?
> >
> > 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* attachments,
> > or just sent as patch series by `git send-email'C, so they apply without
> > having to edit them.
>
> Sorry ...
>
> My regular MUA does not support 'In-Reply-to' ...
>
> 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 thread.
`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.
>
> Next time I will do both. Respond to the thread with a reply that will refer
> to a message (sent by my regular MUA) which will have the attachements.
>
> 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
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-06-07 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 19:38 Installing sshd on W7 reveals errors in CSIH_SCRIPT Houder
2017-05-27 11:35 ` Houder
2017-05-27 15:55 ` Installing sshd on W7 reveals errors in CSIH_SCRIPT -- patch file against master Houder
2017-05-28 13:46 ` Houder
2017-06-07 9:15 ` Corinna Vinschen
2017-06-07 11:58 ` Houder
2017-06-07 14:35 ` Corinna Vinschen
2017-06-07 18:17 ` Houder
2017-06-07 18:56 ` Corinna Vinschen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170607185631.GD13513@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).