From: Achim Gratz <Stromeko@NexGo.DE>
To: cygwin@cygwin.com
Subject: Re: snapshot 2013-01-23
Date: Tue, 29 Jan 2013 10:45:00 -0000 [thread overview]
Message-ID: <loom.20130129T114207-393@post.gmane.org> (raw)
In-Reply-To: <loom.20130128T145147-619@post.gmane.org>
Achim Gratz <Stromeko <at> NexGo.DE> writes:
> I'm seeing strange behaviour from lftp scripts that use external commands;
The problem with lftp goes away when I roll back to the snapshot 2013-01-07, the
one from 2013-01-18 is also bad. I did not test any in-between snapshots. I
don't know yet if the problem with Git was related or not.
Regards,
Achim.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2013-01-29 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 13:59 Achim Gratz
2013-01-28 14:57 ` Achim Gratz
2013-01-29 12:47 ` Achim Gratz
2013-01-30 11:28 ` Achim Gratz
2013-01-31 5:37 ` Christopher Faylor
2013-01-31 8:45 ` Achim Gratz
2013-01-29 10:45 ` Achim Gratz [this message]
2013-01-31 5:35 ` Christopher Faylor
2013-01-31 9:48 ` Achim Gratz
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=loom.20130129T114207-393@post.gmane.org \
--to=stromeko@nexgo.de \
--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).