ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: SASADA Koichi <ko1@atdot.net>
To: ruby-core@ruby-lang.org, ruby-dev@ruby-lang.org
Subject: [ruby-core:71297] DevelopersMeeting20151109Japan¶
Date: Mon, 2 Nov 2015 19:53:13 +0900	[thread overview]
Message-ID: <56374099.2010207@atdot.net> (raw)

Hi,

We will hold dev-meeting at 2015/11/09 (Mon) 14:00- JST in Tokyo, Japan.
Sorry discussion will be in Japanese, but we will write a log in English
(as much as I can).

Please add your concerning tickets in agenda if you have.

Note that this meeting is *NOT* decision making place. All of conclusion
will be filed in bug tracker.

Thanks,
Koichi

Details:
https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeeting20151109Japan
-- 
// SASADA Koichi at atdot dot net

             reply	other threads:[~2015-11-02 10:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 10:53 SASADA Koichi [this message]
2015-11-09  9:06 ` [ruby-core:71409] Re: DevelopersMeeting20151109Japan¶ SASADA Koichi

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=56374099.2010207@atdot.net \
    --to=ruby-core@ruby-lang.org \
    --cc=ruby-dev@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).