Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>
To: Hamish D <dmishd@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] replacement sup wiki
Date: Sun, 13 Jan 2013 22:06:03 +0100	[thread overview]
Message-ID: <CAMiZLn248BGp9ZZ9_xRC2O=V150J+7jEA6j6+0mmJOfDMCFxfA@mail.gmail.com> (raw)
In-Reply-To: <CAOxvSbeLBiP9pGgpLek0AKfSSdUvG8Zix+Ly5wrNTDLQ-XuUZQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 488 bytes --]

 This is excellent news, thank you for the move! I was myself considering
running our own bugtracker, seeing that wmorgan's github hasn't been
updated in the last 7 months and he is the only one being able to act on
them. Same thing would have to be done for the mailing-lists.

Speaking of the mailing list, is it okay if we hijack the wiki with
heliotrope content ? I read too many complaints about it being too hard to
install/use, and would love to fix it.


-- 
Matthieu RAKOTOJAONA

[-- Attachment #1.2: Type: text/html, Size: 608 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  reply	other threads:[~2013-01-13 21:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-13 15:22 Hamish D
2013-01-13 21:06 ` Matthieu Rakotojaona [this message]
2013-01-13 23:40   ` Hamish D
2013-01-14  8:51     ` Gaute Hope
2013-01-14 13:20       ` Philippe LeCavalier
2013-02-01  9:54 ` Gaute Hope
2013-02-03 19:10   ` Hamish D
2013-02-04 13:35     ` Matthieu Rakotojaona

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='CAMiZLn248BGp9ZZ9_xRC2O=V150J+7jEA6j6+0mmJOfDMCFxfA@mail.gmail.com' \
    --to=matthieu.rakotojaona@gmail.com \
    --cc=dmishd@gmail.com \
    --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