git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Jonas Flodén" <jonas.floden@gmail.com>,
	"SZEDER Gábor" <szeder@ira.uka.de>
Subject: [PATCH] Documentation: minor cleanup in a use case in 'git stash' manual
Date: Tue,  2 Sep 2008 03:45:01 +0200	[thread overview]
Message-ID: <1220319901-23733-1-git-send-email-szeder@ira.uka.de> (raw)
In-Reply-To: <1220319324-23012-1-git-send-email-szeder@ira.uka.de>

There is no need to explicitly pass the file to be committed to 'git
commit', because it's contents is already in the index.

Signed-off-by: SZEDER Gábor <szeder@ira.uka.de>
---

  Ah, and one more small change in stash docs.

 Documentation/git-stash.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Documentation/git-stash.txt b/Documentation/git-stash.txt
index cdf3cf1..f91368c 100644
--- a/Documentation/git-stash.txt
+++ b/Documentation/git-stash.txt
@@ -207,7 +207,7 @@ each change before committing:
 $ git add --patch foo            # add just first part to the index
 $ git stash save --keep-index    # save all other changes to the stash
 $ edit/build/test first part
-$ git commit foo -m 'First part' # commit fully tested change
+$ git commit -m 'First part'     # commit fully tested change
 $ git stash pop                  # prepare to work on all other changes
 # ... repeat above five steps until one commit remains ...
 $ edit/build/test remaining parts
-- 
1.6.0.1.171.gaaac

  reply	other threads:[~2008-09-02  1:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 23:14 Unexpected behaviour with git stash save --keep-index? Jonas Flodén
2008-09-02  1:28 ` SZEDER Gábor
2008-09-02  1:35   ` [PATCH] Documentation: fix disappeared lines in 'git stash' manpage SZEDER Gábor
2008-09-02  1:45     ` SZEDER Gábor [this message]
2008-09-02  6:20   ` Unexpected behaviour with git stash save --keep-index? Jonas Flodén
2008-09-02  7:45 ` Karl Hasselström

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1220319901-23733-1-git-send-email-szeder@ira.uka.de \
    --to=szeder@ira.uka.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jonas.floden@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).