../docs/tasks.html. There is also a

../docs/maintain/index.html and ../docs/git/index.html."); ?>

This also contains the documentation:"); ?>

git clone
Browse repository via web

Documentation is in the other repository:"); ?>

git clone
Browse repository via web

General guidelines for submitting patches

this article. You can use an alias, or your company name (if you have a company), if you want. Also, read this article."); ?>

When submitting any kind of documentation, please try not to use the terms him/her, she/he, his/her. Use their, they, them, those people, that person, and so on. You are making a huge difference.

copyleft preferred)."); ?> https://www.gnu.org/licenses/license-list.html.

Small technical note: libreboot is working to convert all documentation to texinfo, where it is currently written in HTML, directly. Therefore, please submit any new documentation under this format, during the transition period.

Information about maintainers to notify, when submitting patches, can be found on the project maintainers page. Generally speaking, libreboot uses a very informal review method for patches. Most patches are merged, unless they obviously have problems. We recommend submitting them to the libreboot development mailing list, linked to from the home page.

Libreboot uses git, a distributed version control system that is in wide use today. Git provides many practical benefits, making collective development of software very easy.

git documentation describes how to use git. The following notes include simple tips for how to use git, but it is a good idea to get fully acquainted with git."); ?>

$ git config --global user.name "Your Name"
$ git config --global user.email your@emailaddress.com
NOTE: you don't have to use your legal name. We don't care what name you use.

$ git config --global core.editor nano
$ git config --global color.status auto
$ git config --global color.branch auto
$ git config --global color.interactive auto
$ git config --global color.diff auto

$ git status

git add path/to/file. You should also add any other files that are listed as modified in the git status. If there are deleted files in the git status, you can use git rm path/to/file. As long as you have added all the untracked files, it is generally easier to use:"); ?>
$ git commit -a
git commit)"); ?>

$ git commit --amend

$ git commit -a --amend

$ git log

$ git config --global --add alias.lol "log --graph --decorate --pretty=oneline --abbrev-commit --all"

$ git lol
git log, but it's much better and shows branches, etc."); ?>

$ git clone "; ?>

$ git clone "; ?>