[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: BUG REPORT("COPY TO" BRANCH FROM TRUNK MERGING BACK TO TRUNK WITHOUT ERROR MESSAGE IF BRANCH FOLDER ALREADY EXISTS)

From: Vincze Péter <vinczepetertamas_at_gmail.com>
Date: Wed, 23 Jul 2014 14:41:49 +0200

I feel myself totally idiot. I tried to reconstruct what I remembered as
happened, and I can not. Sorry, please delete this from mailing list.

2014-07-23 11:46 GMT+02:00 Simon Large <simon.tortoisesvn_at_gmail.com>:

> On 23 July 2014 10:13, Vincze Péter <vinczepetertamas_at_gmail.com> wrote:
> > Hello!
> >
> > Thanks for reply, and I hope actually I'm writing directly to You is
> > acceptable.
>
> Actually you are replying to the mailing list which is the correct
> thing to do. Replying directly is not ;-)
>
> > Yes, I have sent 3 times, as once it was showing up, once again as 2
> hours
> > later did not, and I just did not know why, and simply sent again, but
> then
> > was showing up twice...so now, I know what not to do.
> >
> > So..you wrote me, how to bug report I hope, actually I can do it the
> right
> > way:
> >
> > 1. I was right clicking on a local working copy(TRUNK), and the shown
> menu I
> > choosed Repo browser
> > 2. I was going up 1 level in the repo, to be able to see trunk as a
> Folder
> > 3. I was right clicking on TRUNK
> > 4. I choosed COPY TO ...
> > 5. This was showing up the copy to dialog as recently, and I wrote the
> same
> > repo, but to point to branches folder instead of trunk, and I was giving
> a
> > folder name
> > At this point I did not know, that the folder name what I was writing
> > ($reponame/branches/BUGFIX_188345) is already exits
> > And when I was clicking on Ok, it seemed that did do nothing, or simply
> did
> > what I wanted, but I've forgotten, that the earlier worked me at thos
> point
> > that wanted a commit message, but actually it did not showing up. But
> this
> > was only later realized, as at this point I simply dif not know what
> > heppened: The earlier created, already existed branch was merging back to
> > trunk.
>
> OK, I have tried to reproduce this in a test repository and it behaves
> as expected for me. The first time I copy trunk to BUGFIX_1, it asks
> me for a commit message and after committing I have a copy of trunk in
> branches with the name of BUGFIX_1.
>
> Now I repeat the operation, copy trunk to branches/BUGFIX_1 as if I
> had forgotten about the first time I did it. Again I get asked for a
> commit message and after committing I have a copy of trunk
> *underneath* branches/BUGFIX_1.
>
> trunk/
> -- Readme.txt
> branches/
> -- BUGFIX_1/
> -- Readme.txt
> -- trunk/
> -- Readme.txt
>
> This maybe not be what you want but it is expected, the same as if you
> use a command line copy:
>
> copy c:/temp c:/temp2 [ creates a copy of c:/temp with a new name,
> c:/temp2 ]
> copy c:/temp c:/temp2 [ creates another copy of c:/temp below
> c:/temp2 with name temp ]
>
> > The way what I suggest to be functioning, if an already existed folder
> found
> > on thos operation would be the same as earlier: A popup showing up an
> error
> > message: Folder already exists!
>
> It is not exactly an error, but it may be possible to make the result
> clearer at the top of the commit dialog. Following the steps that I
> took, in both cases the commit dialog shows:
>
> Copy file:///C:/Temp/repos2/trunk_at_HEAD
> to file:///C:/Temp/repos2/branches/BUGFIX_1
>
> Even though the results are different. It should be possible to know
> whether the path exists and in the second case show
>
> Copy file:///C:/Temp/repos2/trunk_at_HEAD
> to file:///C:/Temp/repos2/branches/BUGFIX_1/trunk
>
> I don't think it is possible to give a warning because people
> structure their repos in different ways, so a legitimate copy which
> goes into an existing folder and does not change the name might be:
>
> svn cp /repos/project1/trunk/mylib /repos/project2/trunk
>
> Trying to guess when a user is doing something they did not intend is
> almost impossible.
>
> > By the way later I recognized, that I can somehow figure out what
> happened,
> > as if no commit message was showing up, than the copy to operation from
> > trunk to branches was merging back to trunk, but of course I did not want
> > that, so I have to reset trunk. And by the way log shows I did a merge
> > operation, not a copy to, so I could not say to my boss, that no, I did
> not
> > do merge back to trunk, as I made a copy to operation.
>
> Merge is a working copy operation. You cannot do it in the repo
> browser by mistake. Something else is going on here.
>
> Simon
>
> ------------------------------------------------------
>
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3085666
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe_at_tortoisesvn.tigris.org].
>

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3085672

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-07-23 14:42:02 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.