[#75225] [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7) — k@...
Issue #12324 has been reported by Kazuki Yamaguchi.
6 messages
2016/04/27
[#78693] Re: [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7)
— Eric Wong <normalperson@...>
2016/12/17
k@rhe.jp wrote:
[#78701] Re: [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7)
— Kazuki Yamaguchi <k@...>
2016/12/17
On Sat, Dec 17, 2016 at 01:31:12AM +0000, Eric Wong wrote:
[#78702] Re: [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7)
— Eric Wong <normalperson@...>
2016/12/17
Kazuki Yamaguchi <k@rhe.jp> wrote:
[ruby-core:75164] Re: [Ruby trunk Misc#12283] Obsolete ChangeLog and commit message in Git-style
From:
Eric Wong <normalperson@...>
Date:
2016-04-24 18:36:27 UTC
List:
ruby-core #75164
naruse@airemix.jp wrote: > Shyouhei Urabe wrote: > > Seems no one is against abandoning ChangeLog. > > > > What about "a ChangeLog-like plain-text file" part? I don't think it's useful given how prevalent git and SVN are among developers. NEWS is much more useful to end users. > One idea is just `svn log -rHEAD:53286`, and we can customize the format further. > (I use git show `git merge-base trunk origin/ruby_2_3` to show the commit) > > TODO: > * How to get the beginning revision of the branch with subversion. We can document that in NEWS. Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>