aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2014-03-20 14:33:42 +0100
committerMattias Andrée <maandree@operamail.com>2014-03-20 14:33:42 +0100
commit7d55625ec14eb88f369a5b0e63d0463a5c18e57d (patch)
tree17db9b8a0ddefd5c3dd7339c602fa42f81072bac
parentm (diff)
downloadusing-git-7d55625ec14eb88f369a5b0e63d0463a5c18e57d.tar.gz
using-git-7d55625ec14eb88f369a5b0e63d0463a5c18e57d.tar.bz2
using-git-7d55625ec14eb88f369a5b0e63d0463a5c18e57d.tar.xz
explain why you should not squash non-tips
Signed-off-by: Mattias Andrée <maandree@operamail.com>
-rw-r--r--using-git.texinfo5
1 files changed, 4 insertions, 1 deletions
diff --git a/using-git.texinfo b/using-git.texinfo
index c373b4c..600b09c 100644
--- a/using-git.texinfo
+++ b/using-git.texinfo
@@ -1459,7 +1459,10 @@ and update the new commit. Without
Try to avoid commit squashing
were the squash top is not the tip
-of a commit chain.
+of a commit chain. It will probably
+lead to merge conflicts and you will
+have interate the process for
+subsequent commits.