I'm really disappointed by this. I do not like the way you got things
going (and also I really do not like to write a message like this).

I asked you to discuss further before rashly committing it. Didn't I?
People actually provided some useful proposals to improve your draft.
However, instead of finding a point of agreement, you shutted down
discussion one-sidedly:


then you became silent. I supposed that you discarded your draft, or
you were reconsidering it in accordance with what people pointed out.
However, as a result, you committed it almost unchanged from your
original draft in the end. You did not show us even a single revised

What is your purpose to participate the project? To make things better,
or, to get everything your own way?

This case of README.md is not a critical matter. However, consider if
a problem is more serious, that is, some technical conflict occurs.
How do you make people believe that you are not a person who commits
arbitrary codes before the achievement of an agreement?

We are forbidden to revert anything committed by others. I sincerely
beg you to consider what this rule means. Please do not disrespect the
community for which we bear the responsibility.


On 2018/10/22 6:25, Maya Rashish wrote:
Module Name:    src
Committed By:   maya
Date:           Sun Oct 21 21:25:53 UTC 2018

Added Files:
        src: README.md

Log Message:
Add a README.md.

This document attempts to describe some commonly needed use-cases.
The build.sh command is opinionated but it's for the sake of having
a command that can be copied and probably works without needing to
inform the user about what various options do.

Discussed in tech-toolchain. I've added some links suggested by kamil
and switched to calling arm64 'aarch64' as requested by richard earnshaw.

To generate a diff of this commit:
cvs rdiff -u -r0 -r1.1 src/README.md

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Reply via email to