On Thu, Jul 30, 2009 at 07:01:37PM +0200, FEJES Jozsef wrote:
> I think a found a bug, and I'm asking you to confirm. Suppose we have an
> up-to-date, versioned directory with a file Program.cs in it. Now let's
> create a new file, x.txt, and do 'svn add x.txt'. Don't commit yet. Make
> a copy of both files: 'svn copy Program.cs Program2.cs' and 'svn copy
> x.txt x2.txt'. Here's the output of 'svn status':
>
> A x.txt
> A x2.txt
> A + Program2.cs
>
> My point: when copying a file already under version control, copy
> behaves as I expect it, there's a link in SVN, the + sign indicates
> that, but when copying a file not committed yet, there's no link, it's
> treated as a completely new file, no + sign.
You haven't committed x.txt, right? So it doesn't have any history, so
svn doesn't mark a copy of it as having history. What do you think svn
should do instead?
Is there a real use case here, or is this all hypothetical?
tyler
Received on 2009-07-30 19:21:12 CEST