From: "Dmitry Semyonov" <linulin@gmail.com>
To: cygwin@cygwin.com
Subject: Re: automate SSH-HOST-CONFIG
Date: Sat, 10 Jan 2009 11:53:00 -0000 [thread overview]
Message-ID: <ddc185be0901100020t257b7936s89a515df430d68b0@mail.gmail.com> (raw)
In-Reply-To: <21383170.post@talk.nabble.com>
On Sat, Jan 10, 2009 at 03:34, blazt wrote:
> How can I automate this process?
Create 'expect' script. You'll likely have to update it here and there
after ssh-host-config upgrades though.
--
...Bye..Dmitry.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2009-01-10 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 5:29 blazt
2009-01-10 11:53 ` Dmitry Semyonov [this message]
2009-01-13 2:31 ` blazt
2009-01-13 9:45 ` Dmitry Semyonov
2009-01-13 19:21 ` blazt
2009-01-16 2:20 ` Dmitry Semyonov
2009-01-16 3:01 ` blazt
2009-01-16 21:02 ` blazt
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=ddc185be0901100020t257b7936s89a515df430d68b0@mail.gmail.com \
--to=linulin@gmail.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).