Mercurial question

[Adrian Klaver]

On 04/08/2016 10:17 AM, Ryan Bain wrote:
> Hello,
>
>              We are currently using mercurial and we have accidentally
> copied a file from one repository to another(hg copy I believe). What it
> has done is to drag history from the previous version when it should
> have been a completely new file. Is there a way to force the new file to
> “unlink” from the old file so that it doesn’t overwrite the version in
> the new repository
>
> What is should be:
>
> Repo v2.3                    Repo v3.0
>
> Version2.3.sql à      Version2.3.sql
>
> Version 3.0.sql (New File)
>
> What it is:
>
> Repo v2.3                    Repo v3.0
>
> Version2.3.sql à      Version 3.0.sql

Can you give some background on the above?

In particular how Repo v3.0 came to be?

How in the 'should be' case Version2.3.sql was supposed to get into Repo 
v3.0?

At this point is Version 3.0.sql really different from Version2.3.sql?


>
> *Ryan Bain *
>
> Micro Technologies
>
> Software Developer
>
> 8701 Center Port Blvd.
>
> Amarillo, Texas, 79108
>
> Work: 806.372.2369
>
> Fax: 806.378.5512
>
> microtechnologies.com
>
>
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial
>


-- 
Adrian Klaver
adrian.klaver at aklaver.com