[#79440] [Ruby trunk Bug#13188] Reinitialize Ruby VM. — shyouhei@...
Issue #13188 has been updated by Shyouhei Urabe.
6 messages
2017/02/06
[#79441] Re: [Ruby trunk Bug#13188] Reinitialize Ruby VM.
— SASADA Koichi <ko1@...>
2017/02/06
On 2017/02/06 10:10, shyouhei@ruby-lang.org wrote:
[#79532] Immutable Strings vs Symbols — Daniel Ferreira <subtileos@...>
Hi,
15 messages
2017/02/15
[#79541] Re: Immutable Strings vs Symbols
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2017/02/15
Em 15-02-2017 05:05, Daniel Ferreira escreveu:
[#79543] Re: Immutable Strings vs Symbols
— Daniel Ferreira <subtileos@...>
2017/02/16
Hi Rodrigo,
[#79560] Re: Immutable Strings vs Symbols
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2017/02/16
Em 15-02-2017 22:39, Daniel Ferreira escreveu:
[ruby-core:79428] Re: [Ruby trunk Bug#13189] [DOC] Restore class documentation for Struct
From:
Eric Wong <normalperson@...>
Date:
2017-02-04 09:05:35 UTC
List:
ruby-core #79428
sto.mar@web.de wrote:
> @normal (@Anonymous)
>
> Regarding commit messages / further explanations:
>
> I wasn't aware that the complete description would be included
> in the commit message; is there a preferred way on
> bugs.ruby-lang.org for providing a (suggested) commit message
> and additional, more verbose explanations?
Yes, I prefer that, at least. Having to go online or even go
out-of-band into my mail archives to look for the explanation of
change is often inconvenient. Explaining in commit message is
is analogous to the inline-cache in YARV to improve locality :)
Anyways, it is expected for git.git (and linux.git) for commit
messages to be complete enough to justify a change.
To the contrary, I dislike GNU ChangeLog entry style used in
Ruby ("make change"). GNU-style describes what changed; but
what changed should already be obvious from reading a diff.
The "why" is not always obvious, and should be explained.
For Ruby, I try to remember to do both (why and what) because
matz liked GNU-style entries, and nobody complained about my
commit messages being too informative :)
If you wish (and it would make my life as patch applyer easier :)
you may use "git format-patch" to generate the patch with
full commit message or use "git request-pull" to format a pull
request pointing to any anonymously-accessible git server.
I will also try to remember to use --add-author-from option
with "git svn" to give you proper credit :x
> (On GitHub there is a natural distinction between the
> commit message and the PR description, but not for Redmine.)
For a single change, I prefer the commit message cover everything.
For multiple changes, an overview of the series along with
"git request-pull" helps summarize the changes.
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>