Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marc.hartstein@alum.vassar.edu (Marc Hartstein)
Subject: [sup-talk] Workaround for sup-config crash in 0.4 on some platforms
Date: Thu, 10 Apr 2008 11:39:36 -0400	[thread overview]
Message-ID: <1207841677-sup-2645@cabinet> (raw)
In-Reply-To: <1207440368-sup-9724@south>

Excerpts from William Morgan's message of Sat Apr 05 20:06:28 -0400 2008:
> Reformatted excerpts from Marc Hartstein's message of 2008-04-04:
> > While updating to git is supposed to correct this problem, many people
> > won't want to go to that effort just to see if sup even works.
> 
> Guess that means it's time to release an 0.5!

Good idea.

I've just confirmed that this problem is fixed in 'master' on my Gentoo
system.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080410/d9cf310f/attachment.bin 


  reply	other threads:[~2008-04-10 15:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 21:43 Marc Hartstein
2008-04-06  0:06 ` William Morgan
2008-04-10 15:39   ` Marc Hartstein [this message]
2008-04-20 22:26     ` William Morgan

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=1207841677-sup-2645@cabinet \
    --to=marc.hartstein@alum.vassar.edu \
    /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