"bzr merge" and "bzr log -n0"

[Stephen J. Turnbull]

Matthew D. Fuller writes:
 > On Sun, Aug 29, 2010 at 01:02:15AM -0400 I heard the voice of
 > Eli Zaretskii, and lo! it spake thus:
 > > Also, is there a particular reason why cherrypicks are not
 > > tracked, or was it a more or less arbitrary design decision?

 > Because there's nowhere to track them.  History is all accessed by
 > dereferencing parent pointers on the revisions, so the presence of
 > one state implies the presence of all its predecessors.  If we
 > don't want to have 2, we can't claim to have 4.

True, first-class cherrypicks are hard unless everything is
patch-based, as in Darcs.

However, you can track them as patches creating new revisions, and
optionally automatically add a note to the commit log giving the
revision they were cherrypicked from.