Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Sven Schober <sven.schober@uni-ulm.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] curses pinentry woes (still)
Date: Thu, 18 Feb 2010 19:35:24 +0100	[thread overview]
Message-ID: <1266518077-sup-3488@hysbald> (raw)
In-Reply-To: <1266516237-sup-7845@midna.zekjur.net>

Excerpts from Michael Stapelberg's message of Thu Feb 18 19:10:07 +0100 2010:
> Could anyone with a little more insight into ruby threads have a look at this
> issue please?

+1

> Best regards,
> Michael

Ciao,
 Sven
-- 
Sven Schober, sven.schober@uni-ulm.de                    |UNI ULM
http://www-vs.informatik.uni-ulm.de/dept/staff/schober/  |DISTRIBUTED
Room O27-346, Phone: +49-731-5024146 [+49-179-5060182]   |SYSTEMS LAB
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-02-18 18:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-07 19:10 Sven Moritz Hallberg
2010-02-07 20:25 ` Michael Stapelberg
2010-02-18 18:10   ` Michael Stapelberg
2010-02-18 18:35     ` Sven Schober [this message]
2010-02-19  3:29       ` Michael Stapelberg
2010-02-19 10:30         ` Sven Schober
2010-02-21 11:13           ` Sven Schober

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=1266518077-sup-3488@hysbald \
    --to=sven.schober@uni-ulm.de \
    --cc=sup-talk@rubyforge.org \
    /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