[PATCH 0/2] Clarify some of the fixup! documenation
- From
Philip Oakley <philipoakley@iee.email>
- Date
- May 25, 2020, 21:36 UTC
- Message-ID
- <20200525213632.1626-1-philipoakley@iee.email>
- In-Reply-To
- <9a9e7432-7a74-f46e-9a77-b8acaa9a974f@iee.email>
It's easy to think that all fixup! commit messages must match a previous subject line based on commit's --fixup option. It had this developer confused for many years.
Lets at least do a some small changes to make the use of the commit hash in the fixup message more obvious.
Philip
In-Reply-To: 9a9e7432-7a74-f46e-9a77-b8acaa9a974f@iee.email To: git@vger.kernel.org cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com> cc: Andrei Rybak <rybak.a.v@gmail.com> cc: Paul Ganssle <paul@ganssle.io> cc: Jeff King <peff@peff.net>
Philip Oakley (2): doc: fixup/squash: clarify use of <oid-hash> in subject line doc: fixup/squash: remove ellipsis marks, use <line> for clarify
Documentation/git-rebase.txt | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-)
-- 2.26.2.windows.1.13.g9dddff6983