public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Please test snapshots
Date: Fri, 10 Aug 2012 18:12:00 -0000	[thread overview]
Message-ID: <87r4reocjf.fsf@Rainer.invalid> (raw)
In-Reply-To: <20120810142515.GE11601@ednor.casa.cgf.cx>

Christopher Faylor writes:
> You're not really giving us much to go on.

I don't have anything else, these are the only two (small) issues I've
seen after installation of the latest snapshot.

> A <defunct> process doesn't mean that something is not properly
> terminated.  Is this also a tcsh shell running git?

Actually it was make started in tcsh, which then forked git (I think it
goes through bash for this, but I'm not sure).  I've killed make while
git was running.  Anyway, the computer will be freshly booted on Monday,
I'll see if that is still reproduceable then.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


--
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

  reply	other threads:[~2012-08-10 17:58 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06  3:53 Christopher Faylor
2012-08-06  5:14 ` Daniel Colascione
2012-08-06  8:59 ` Achim Gratz
2012-08-08 13:04   ` Achim Gratz
2012-08-09  8:07     ` Achim Gratz
2012-08-06 15:31 ` Filipp Gunbin
2012-08-06 23:27   ` Daniel Colascione
2012-08-07  0:39     ` Daniel Colascione
2012-08-07  0:40       ` Daniel Colascione
2012-08-08 22:17       ` Christopher Faylor
2012-08-09  6:35         ` Daniel Colascione
2012-08-09 12:29         ` Achim Gratz
2012-08-09 14:54           ` Christopher Faylor
2012-08-09 15:06             ` Achim Gratz
2012-08-09 14:59           ` Daniel Colascione
2012-08-10  7:15             ` Achim Gratz
2012-08-10 14:36               ` Christopher Faylor
2012-08-10 18:12                 ` Achim Gratz [this message]
2012-08-10 18:34                   ` Christopher Faylor
2012-08-10 19:08                     ` Achim Gratz
2012-08-10 20:24                       ` Christopher Faylor
2012-08-10 20:37                         ` Achim Gratz
2012-08-10 23:31                           ` Christopher Faylor
2012-08-14 13:45                 ` Adam Dinwoodie
2012-08-16 19:01                   ` Christopher Faylor
2012-08-16 19:33                     ` Ken Brown
2012-08-16 19:45                       ` Christopher Faylor
2012-08-16 20:11                         ` Ken Brown
2012-08-17  9:38                     ` Adam Dinwoodie
2012-08-17 14:37                       ` Christopher Faylor
2012-08-17 17:46                         ` Adam Dinwoodie
2012-08-17 18:08                           ` Christopher Faylor
2012-08-17 19:32                         ` Achim Gratz
2012-08-17  9:40           ` Achim Gratz
2012-08-17 10:47             ` Achim Gratz
2012-08-14 19:23 ` jojelino
2012-08-14 19:41   ` Corinna Vinschen
2012-08-14 19:42     ` Christopher Faylor

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=87r4reocjf.fsf@Rainer.invalid \
    --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).