ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
To: ruby-core@ruby-lang.org
Cc: "halorgium (Tim Carey-Smith)" <ruby-lang@spam.halorgium.net>
Subject: [ruby-core:54460] moving issues (was: [ruby-trunk - Feature #8215] Support accessing Fiber-locals and backtraces for a Fiber)
Date: Fri, 19 Apr 2013 16:01:51 +0900	[thread overview]
Message-ID: <5170EBC7.1060502@it.aoyama.ac.jp> (raw)
In-Reply-To: <redmine.journal-38739.20130419155002@ruby-lang.org>

On 2013/04/19 15:50, halorgium (Tim Carey-Smith) wrote:
>
> Issue #8215 has been updated by halorgium (Tim Carey-Smith).
>
>
> I realised that this might be better in common-ruby.

This isn't issue specific: I propose that just for the moment, issues 
stay where they are. Once the overall directions are sorted out, we can 
organize a general campaign to move issues wherever necessary. If we can 
avoid it, we don't want to pollute each and every issue with individual 
move requests.

Regards,   Martin.

  reply	other threads:[~2013-04-19  7:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 23:47 [ruby-core:53974] [ruby-trunk - Feature #8215][Open] Support accessing Fiber-locals and backtraces for a Fiber halorgium (Tim Carey-Smith)
2013-04-04 12:50 ` [ruby-core:53990] [ruby-trunk - Feature #8215][Closed] " Eregon (Benoit Daloze)
2013-04-05  9:27 ` [ruby-core:54019] [ruby-trunk - Feature #8215][Open] " nobu (Nobuyoshi Nakada)
2013-04-05 11:06 ` [ruby-core:54021] [ruby-trunk - Feature #8215] " Eregon (Benoit Daloze)
2013-04-07 10:14 ` [ruby-core:54080] " halorgium (Tim Carey-Smith)
2013-04-09  7:33 ` [ruby-core:54133] " nobu (Nobuyoshi Nakada)
2013-04-16  8:03 ` [ruby-core:54329] " nobu (Nobuyoshi Nakada)
2013-04-19  6:50 ` [ruby-core:54457] " halorgium (Tim Carey-Smith)
2013-04-19  7:01   ` "Martin J. Dürst" [this message]
2013-06-02  6:45 ` [ruby-core:55237] [ruby-trunk - Feature #8215][Assigned] " zzak (Zachary Scott)
2020-01-05 22:51 ` [ruby-core:96674] [Ruby master Feature#8215] " samuel
2020-01-05 22:51 ` [ruby-core:96675] " samuel
2020-01-06 18:22 ` [ruby-core:96693] " eregontp
2020-01-06 20:50 ` [ruby-core:96694] " samuel

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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5170EBC7.1060502@it.aoyama.ac.jp \
    --to=ruby-core@ruby-lang.org \
    --cc=ruby-lang@spam.halorgium.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).