| Age | Commit message (Collapse) | Author |
|
* [DOC] Languages in Examples
* Update doc/contributing/documentation_guide.md
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
* Update doc/contributing/documentation_guide.md
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
---------
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
|
|
Re-organize page docs
|
|
|
|
|
|
This guide is for those that want to contribute to ruby but don't
understand where they need to use locks or other concurrency mechanisms.
It teaches them how to use these locks safely and what is prohibited in
certain circumstances.
|
|
CSV is no more part of the standard lib, but the documentation was not
updated (the example link was broken for the master branch)
Selected ERB that has the dedicated directory, like CSV.
|
|
|
|
|
|
ASAN works on Ruby 3.4 and later, so we can remove the point about using
master branch for ASAN.
|
|
|
|
|
|
Since RDoc's documentation is built separately now, the references will
no longer work.
|
|
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13129
|
|
Notes:
Merged-By: peterzhu2118 <peter@peterzhu.ca>
|
|
I had issues building Ruby as I was using git 2.30.
The error was:
> file2lastrev.rb: git rev-parse failed error: could not expand
> include path '~/.gitcinclude'
The default system git config includes paths making use of `$HOME`,
but that env variable gets removed when building: https://github.com/ruby/ruby/blob/7070b1b1968f31f999636b42a1af872458cd5a81/tool/lib/vcs.rb#L546-L547
It works with git `>= 2.32` thanks to the `GIT_CONFIG_SYSTEM`
feature which gets set to a Null IO in order to override
the system gitconfig. https://github.com/ruby/ruby/blob/7070b1b1968f31f999636b42a1af872458cd5a81/tool/lib/vcs.rb#L549
Notes:
Merged: https://github.com/ruby/ruby/pull/12611
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12586
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12496
|
|
* Clarify “Building Ruby” docs
* Fix test examples to work from `build` dir
* Clarify “Testing Ruby” examples with real examples
All the commands should run correctly by default, without the user needing to modify them. This builds confidence that the relative paths are working correct from within the `build` directory.
Also, let’s use a consistent example throughout, for greater clarity.
* Improve examples to use `-v` flag in-context
This shows the correct way to combine `-v` with another parameter, e.g. a specific file to test.
* Other readability improvements
* Clarify `make` implementation support
|
|
* Fix WASM bullet/code indentation
* Use `console` code highlighting where appropriate
… which handles the prefix `$` correctly.
* Migrate feature proposal template to MarkDown
* Set language on code blocks
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12059
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11330
|
|
Notes:
Merged-By: peterzhu2118 <peter@peterzhu.ca>
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11261
|
|
|
|
|
|
- `OpenSSL` here is not the class.
- libexecinfo on FreeBSD is present in the base system of all
supported releases, since 2017.
|
|
Get rid of using ambiguous demonstratives as link anchors, for the
accessibility's sake.
|
|
|
|
|
|
Clang 18 has the bugfix we need, so we no longer need to tell people to
compile Clang from source.
|
|
|
|
https://blade.ruby-lang.org/ruby-dev/39325
|
|
|
|
|
|
|
|
s/copmiler-rt/compiler-rt/
|
|
|
|
I don't really think ASAN works well at all on any version of Ruby from
before https://bugs.ruby-lang.org/issues/20001 was landed. Update the
docs to clarify what works, and what does not work.
Also there's no need to compile at `-O0`; this was probably just hiding
some of the problems with our stack scanning that were fixed in the
above issue.
[Bug #20248]
|
|
|
|
|
|
* More on What's Here
* More on What's Here
|
|
|
|
following up on https://github.com/ruby/ruby/pull/8832
|
|
Looking at building_ruby.md it is unclear that you are able to build Ruby on Windows. To fix that a reference has been added to the windows.md file.
|
|
|
|
It might not be obvious how to get the build directory and the Makefile
set up.
|