typos in code of conduct

This commit is contained in:
reaction.la 2023-02-24 11:21:15 +08:00
parent a9d34c3f0b
commit 98a0c6a5f7
No known key found for this signature in database
GPG Key ID: 99914792148C8388
3 changed files with 10 additions and 13 deletions

View File

@ -6,8 +6,8 @@
whitespace = fix whitespace = fix
ignoreWhitespace = no ignoreWhitespace = no
[alias] [alias]
lg = log --max-count=6 --oneline --pretty='format:%C(auto)%h %d %Creset%p %C("#60A0FF")%cr %Cgreen %cn %G? %GT trust%Creset%n%s%n' lg = log --max-count=6 --pretty=format:'%C(auto)%h %d %Creset %p %C("#60A0FF")%cr %Cgreen %cn %G? %GT trust%Creset%n %<(78,trunc)%s%n'
graph = log --max-count=18 --graph --pretty=format:'%C(auto)%h %s %Cgreen(%cr) %C(bold blue)%cn %G?%Creset' --abbrev-commit graph = log --max-count=38 --graph --pretty=format:'%C(auto)%h %<(78,trunc)%s %Cgreen(%cr) %C(bold blue)%cn %G?%Creset' --abbrev-commit
alias = ! git config --get-regexp ^alias\\. | sed -e s/^alias\\.// -e s/\\ /\\ =\\ / | grep -v ^'alias ' | sort alias = ! git config --get-regexp ^alias\\. | sed -e s/^alias\\.// -e s/\\ /\\ =\\ / | grep -v ^'alias ' | sort
[commit] [commit]
gpgSign = true gpgSign = true

View File

@ -83,24 +83,21 @@ tagged commit by the person requesting.
When creating the tag for a pull request, git drops one into an editor and When creating the tag for a pull request, git drops one into an editor and
asks one to describe the tag. One should then give a lengthy description of asks one to describe the tag. One should then give a lengthy description of
one's pull request documenting the changes made. Or, better, the tag one's pull request documenting the changes made.
should already contain a lengthy description of the pull request containing
the changes made.
When accepting a pull request, the information provided by the requestor When accepting a pull request, the information provided by the requestor
through the tag and elsewhere should be duplicated by the acceptor into through the tag and elsewhere should be duplicated by the acceptor into
the (possibly quite lengthy) merge message. Or, better, if he can fast the (possibly quite lengthy) merge message.
forward the pull request, the tag will be the merge message, which will
lead to git recording a more intelligible and linear project history.
Thus all changes should be made, explained, and approved by persons Thus all changes should be made, explained, and approved by persons
identified cryptographically, rather than through the domain name system. identified cryptographically, rather than through the domain name system.
It is preferable to simplify the history recorded in git by rebasing the It is preferable to simplify the history recorded in git by rebasing the
changes in the branch that you want pulled to the most recent version of changes in the branch that you want pulled to the most recent version
the branch that you want it pulled into. This produces an artificially linear signed by the puller of the branch that you want it pulled into. This
history, which is likely to be more intelligible and informative than the produces an artificially linear history, which is likely to be more
actual history. In particular, more intelligible to the person pulling. intelligible and informative than the actual history. In particular, more
intelligible to the person who has been requested to pull.
# No race, sex, religion, nationality, or sexual preference # No race, sex, religion, nationality, or sexual preference

View File

@ -77,7 +77,7 @@ sudo -i
apt-get -qy update && apt-get -qy install build-essential module-assistant git dnsutils curl sudo dialog rsync apt-get -qy update && apt-get -qy install build-essential module-assistant git dnsutils curl sudo dialog rsync
apt-get -qy full-upgrade apt-get -qy full-upgrade
m-a -qi prepare m-a -qi prepare
apt autoremove apt autoremove -qy
mount /media/cdrom0 mount /media/cdrom0
cd /media/cdrom0 && sh ./VBoxLinuxAdditions.run cd /media/cdrom0 && sh ./VBoxLinuxAdditions.run
usermod -a -G vboxsf cherry usermod -a -G vboxsf cherry