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 developers <ruby-core@ruby-lang.org>
Subject: [ruby-core:76662] Re: [Ruby trunk Feature#11337] Allow rescue without begin inside blocks
Date: Tue, 2 Aug 2016 20:20:26 +0900	[thread overview]
Message-ID: <66470680-7d8f-605c-3686-55b5b269a326@it.aoyama.ac.jp> (raw)
In-Reply-To: <redmine.journal-59868.20160802015438.7848873b46c64788@ruby-lang.org>

On 2016/08/02 10:54, shyouhei@ruby-lang.org wrote:

> I guess those duplicated issues synchronizes their status each other so I don't close them (am I correct?).

I guess it depends on how you linked them. If it's just 'related', then 
the status of each is independent. If it's 'depends on', then you can 
close one without closing the other, but not the other way round. But 
I'm not sure this is enforced.

  reply	other threads:[~2016-08-02 10:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-11337.20150707133807@ruby-lang.org>
2015-07-07 13:38 ` [ruby-core:69887] [Ruby trunk - Feature #11337] [Open] Allow rescue without begin inside blocks rr.rosas
2016-08-01 12:58 ` [ruby-core:76639] [Ruby trunk Feature#11337] " rr.rosas
2016-08-02  1:54 ` [ruby-core:76648] " shyouhei
2016-08-02 11:20   ` Martin J. Dürst [this message]
2016-08-03 19:23 ` [ruby-core:76686] " rr.rosas
2016-08-04  9:28   ` [ruby-core:76731] " Martin J. Dürst
2016-08-03 19:24 ` [ruby-core:76687] " rr.rosas
2016-08-04  6:48 ` [ruby-core:76701] [Ruby trunk Feature#11337][Closed] " shyouhei

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=66470680-7d8f-605c-3686-55b5b269a326@it.aoyama.ac.jp \
    --to=ruby-core@ruby-lang.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).