Re: 0.5 draft of new dumnfile docs

Hi Eric,

in the 0.5 draft, there's a paragraph about breaking history the
history of a flow.

[[[
A flow is a sequence of actions on a file or directory path that is
considered to be a single history for change-tracking purposes.
Creating a flow tells Subversion that you want to track the history of
the path or paths it contains. Destroying a flow breaks the chain of
history; changes will not be tracked across the break, even if another
flow is created at the same path.
]]]

You might want to add that flows may be connected by copyfrom info.

The copyfrom info is used by 'svn log', 'svn merge' and other
commands to retrieve the full history of an item.

It's possible to "resurrect" a deleted flow via 'svn copy'. The copyfrom
info will bridge the gap back to the old flow.

  http://svnbook.red-bean.com/en/1.7/svn.branchmerge.basicmerging.html#svn.branchmerge.basicmerging.resurrect

There's also the phenomenon of "evil twins", where an item is replaced
when it should have been changed. Arbitrarily breaking the flow
causes problems because the replace-operation is echoed on branches
by 'svn merge'.

Perhaps reposurgeon will enable us to fix such problems offline, via
git-fast-import support, as discussed on this list recently.

  http://svn.haxx.se/dev/archive-2011-11/0328.shtml

Regards,
Steve

--
Stephen Butler | Consultant
elego Software Solutions GmbH
Gustav-Meyer-Allee 25, 13355 Berlin, Germany
tel: +49 30 2345 8696 | mobile: +49 163 25 45 015
fax: +49 30 2345 8695 | http://www.elego.de
Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin
Amtsgericht Charlottenburg HRB 77719