Pushing after merge considered harmful

[Eli Zaretskii]

> Date: Tue, 26 Jan 2010 09:41:15 +0100
> From: Martin Pool <mbp at canonical.com>
> Cc: Alexander Belchenko <bialix at ukr.net>, bazaar at lists.canonical.com
> 
> It means that you can only change the branch tip pointer from A to B
> if A is in the left-hand history of B.  Left-hand history means the
> history following only the 0th (left-hand) parent pointer; this means
> essentially that you got from A to B by either simple commits or
> commits that merge other things in, not by merging in A.

Thanks.  What does this mean in practice, wrt commands such as
"checkout", "commit", "update", "merge", "pull", and "push"?  Does the
type of the branch (bound or not, lightweight or not) matter?

Alexander gave an example, which is useful because it is based on a
very popular workflow.  But the consequences for less popular
workflows and operations are also important to know.

TIA