Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup 0.12 released
Date: Wed, 26 Jan 2011 14:11:59 -0500	[thread overview]
Message-ID: <1296069110-sup-1872@masanjin.net> (raw)
In-Reply-To: <1296065958-sup-8939@zyrg.net>

Reformatted excerpts from Rich Lane's message of 2011-01-26:
> Yeah, 1.2.4.3 fixes compat.h not being included in menu_wrap.c.

Damn I'm good.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2011-01-26 19:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15  7:07 [sup-devel] " Rich Lane
2011-01-17 10:44 ` [sup-talk] " Shadowfirebird
2011-01-17 22:03   ` Philipp Überbacher
2011-01-18  3:36     ` Rich Lane
2011-01-25 16:24       ` Andrei Thorp
2011-01-25 16:46         ` Andrei Thorp
2011-01-26 15:52           ` William Morgan
2011-01-26 18:22             ` Rich Lane
2011-01-26 19:11               ` William Morgan [this message]
2011-01-26 15:50         ` William Morgan
2011-01-27 18:51           ` Andrei Thorp

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=1296069110-sup-1872@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    --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