From: Takashi Kokubun <takashikkbn@gmail.com>
To: Ruby developers <ruby-core@ruby-lang.org>
Subject: [ruby-core:92787] [ANN] "master" branch created for ruby.git; Use "master" branch instead of "trunk" on CI
Date: Wed, 22 May 2019 08:46:01 -0700 [thread overview]
Message-ID: <CAOM42UehGmhbNC7cu2Cs3A6Q1PUUyFesGkqEj3eFO1SKKrrGCQ@mail.gmail.com> (raw)
Hi ruby-core,
At 0:28 am JST on 5/23, we created a symbolic-ref "master" pointing to
"trunk" on git.ruby-lang.org.
Ruby committers can fetch and push to both "master" and "trunk"
branches with git.ruby-lang.org.
Also everyone can fetch "master" branch with GitHub repository now.
[NOTE] On July 1st, we are going to change the default branch of
ruby.git from "trunk" to "master" on both git.ruby-lang.org and
GitHub.
Before that, please explicitly clone "master" branch instead of
"trunk" if your CI system may break by the change.
See https://bugs.ruby-lang.org/issues/15843 for the future schedule.
Thank you,
k0kubun
reply other threads:[~2019-05-22 15:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAOM42UehGmhbNC7cu2Cs3A6Q1PUUyFesGkqEj3eFO1SKKrrGCQ@mail.gmail.com \
--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).