> And it can happen naturally during refactoring.
> For example, you might want to split a file into two distinct
> files, preserving their common history.
Good point. Thanks.
jamie
===
Please access the attached hype
On Tue, Jan 25, 2011 at 11:36:02AM -, Echlin, Jamie wrote:
> > But doing copy operations within a branch root (i.e. they
> > don't cross branch boundaries) is fine.
>
> Is a copy, as opposed to a rename/move really fine? I'm not sure why
> people would want two files in the same branch to sha
Thanks Stefan, excellent answer.
> It was basically assumed that users would easily grok the UI
> because a "copy" is a simple concept that's also known to
> people who haven't used version control before.
> However, when you also do advanced stuff like merging you
> need to understand how to
On Tue, Jan 25, 2011 at 01:32:30AM -0800, JamieEchlin wrote:
>
> What are the acceptable cases for using svn cp? Superficially, it can be used
> for creating branches or tags, and indirectly as part of a move/rename
> operation, and restoring a deleted file/dir, but are they any other
> justified
Hi Jamie,
as you have already pointed out you lose the mergeinfo - I would say that
this is not acceptable from an auditing point of view, and it also causes
headaches later for the person who has to merge stuff from the branch back
to another branch.
Jon
