From: Sven Schober <sven.schober@uni-ulm.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] curses pinentry woes (still)
Date: Fri, 19 Feb 2010 11:30:49 +0100 [thread overview]
Message-ID: <1266575368-sup-8036@hysbald> (raw)
In-Reply-To: <1266550118-sup-5231@midna.zekjur.net>
Excerpts from Michael Stapelberg's message of Fri Feb 19 04:29:28 +0100 2010:
> In the meantime, I fixed the problem (at least it works for me). You can get my
> patch at sup-devel, see
> http://rubyforge.org/pipermail/sup-devel/2010-February/000373.html
>
Thanks, i'll give it a try :)!
> 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
next prev parent reply other threads:[~2010-02-19 10:31 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
2010-02-19 3:29 ` Michael Stapelberg
2010-02-19 10:30 ` Sven Schober [this message]
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=1266575368-sup-8036@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