From: magnus@therning.org (Magnus Therning)
Subject: [sup-talk] Two small fixes
Date: Wed, 12 Sep 2007 08:06:25 +0100 [thread overview]
Message-ID: <20070912070625.GB3345@die.therning.org> (raw)
In-Reply-To: <1189553292-sup-3297@south>
On Tue, Sep 11, 2007 at 16:28:53 -0700, William Morgan wrote:
>Excerpts from Magnus Therning's message of Thu Sep 06 00:21:59 -0700 2007:
>> Yesterday I ran into some warnings when using sup from SVN:
>
>Fixed, thanks! How did you get the warnings to pop up? I only
>occasionally see warnings for an instant before curses takes over the
>screen...
I'm not sure why the warnings linger long enough for me to catch them.
Could be my choice of terminal (ROXTerm)?
/M
--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus?therning?org Jabber: magnus?therning?gmail?com
http://therning.org/magnus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070912/6124205c/attachment.bin
prev parent reply other threads:[~2007-09-12 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 7:21 Magnus Therning
2007-09-11 23:28 ` William Morgan
2007-09-12 7:06 ` Magnus Therning [this message]
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=20070912070625.GB3345@die.therning.org \
--to=magnus@therning.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