From: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>
To: supmua <supmua@googlegroups.com>
Subject: Re: [sup] Broken sup after gem update
Date: Wed, 11 Mar 2015 22:03:37 +0100 [thread overview]
Message-ID: <1426107763-sup-6280@kpad> (raw)
In-Reply-To: <loom.20150311T035906-536@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
Excerpts from Joe Schlimmer's message of 2015-03-11 03:04:31 +0000:
> I have this exact same problem after updating...
>
Hey everyone,
Joe has kindly opened
https://github.com/sup-heliotrope/sup/issues/403
for easier tracking.
--
Matthieu Rakotojaona
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 343 bytes --]
prev parent reply other threads:[~2015-03-11 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 16:18 gui-gui
2015-03-11 3:04 ` [sup] " Joe Schlimmer
2015-03-11 20:10 ` gui-gui
2015-03-11 21:03 ` Matthieu Rakotojaona [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=1426107763-sup-6280@kpad \
--to=matthieu.rakotojaona@gmail.com \
--cc=supmua@googlegroups.com \
/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