From ae8286f23e2dc1c61eb570058ba9030a48589334 Mon Sep 17 00:00:00 2001 From: Jiri Hubacek Date: Wed, 10 Oct 2018 16:00:31 +0200 Subject: [PATCH] Rewrite summary of build history in introduction --- intro.md | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/intro.md b/intro.md index 4050b82..16202cb 100644 --- a/intro.md +++ b/intro.md @@ -104,15 +104,10 @@ And staged patches by: git diff --cached ``` -# Commit - build repository history -You get ready the files to be commited to the history by `git add FILE` -command. If you change your mind, you may `git reset FILE` that file. - -If only huks of lines in file should be prepared for commiting to the history -`git add -p FILE` and `git reset -p FILE` can be used respectively. - -Before commiting to the history log check twice `git diff --cached` and `git -diff`. +# Build repository history +Use `git commit` to store staged patches to git history. Moving patches and +files between states described above is done by `git add` and `git reset` +commands. When sure that staged changes should be commited to the history, use `git commit -m'COMMIT MSG'`. For commit messages, some rules are good to keep in -- 2.39.2