Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] wrapping in the bottom command line
Date: Tue, 09 Mar 2010 23:07:06 +0100	[thread overview]
Message-ID: <1268172283-sup-3882@midna.zekjur.net> (raw)
In-Reply-To: <1268170953-sup-8766@guava.lanl.gov>

Hi John,

Excerpts from John Bent's message of Di Mär 09 22:44:09 +0100 2010:
> Anyone else seeing this?
Please upgrade to 0.11, the bug is fixed there (see [1]).

Best regards,
Michael

[1] http://gitorious.org/sup/mainline/commit/42e7aeaa907444acfcd1e1c30681c30ccb0cf2f1
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

      parent reply	other threads:[~2010-03-09 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 21:44 John Bent
2010-03-09 21:59 ` Rich Lane
2010-03-09 22:16   ` John Bent
2010-03-09 22:43     ` Michael Stapelberg
2010-03-09 23:15       ` John Bent
2010-03-09 22:07 ` Michael Stapelberg [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=1268172283-sup-3882@midna.zekjur.net \
    --to=michael+sup@stapelberg.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