From 1a0104fc63be891a31493f6d811528ee53b624d0 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Mon, 31 Mar 2008 17:28:23 +0200 Subject: [PATCH] * README-contribution-guidelines: Mention how to amend a commit. MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Suggestion from Pádraig Brady. --- README-contribution-guidelines | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README-contribution-guidelines b/README-contribution-guidelines index c78ded8e7e..bed256f0d8 100644 --- a/README-contribution-guidelines +++ b/README-contribution-guidelines @@ -8,6 +8,9 @@ version 1.4.4, then you'd do well to get a newer version. At worst, just download the latest stable release from http://git.or.cz/ and build from source. +For details on building the programs in this package, see +the file, README-hacking. + Use the latest upstream sources =============================== @@ -166,8 +169,17 @@ the tip of the trunk. Now use git format-patch, as above. +Amending the most recent change on your private branch +====================================================== +Let's say you've just committed a change on your private +branch, and then realize that something about it is not right. +It's easy to adjust: + edit your files # this can include running "git add NEW" or "git rm BAD" + git commit --amend -e -a + git format-patch --stdout --signoff HEAD~1 > your-branch.diff +That replaces the most recent commit with the revised one. -- 2.47.3