Hi I would like to know if the only/easiest way to copy a sourcesafe project including its history is to Share and Branch? I am talking about a copy within the same database. What bothers me with the fact that I can do it using a Share/Branch is that I have the feeling (I am not sure) that they still are connected somehow, which I do not want them to be. So my other question is are they connected, and what consequences can that possibly have? Thanks jeeji
"jeeji" wrote in message news:cbb9e5d9-5e5a-4ac6-b4c9-eaefed3674cc@s19g2000prg.googlegroups.com... > Hi > > I would like to know if the only/easiest way to copy a sourcesafe > project including its history is to Share and Branch? > > I am talking about a copy within the same database. > > What bothers me with the fact that I can do it using a Share/Branch is > that I have the feeling (I am not sure) that they still are connected > somehow, which I do not want them to be. > So my other question is are they connected, and what consequences can > that possibly have? As long as you check "branch after share", all the files will be a new copy branched from the old. --Mark
Hi and thanks for your answer I actually already knew that part. So what I really want to know is: - Is that the only way of copying a project? - If I use the Share/Branch strategy, are there any consequences. What I mean here is are the two branches connected in a way that may have consequences for me, if all I need in the first place is a disconnected copy of the project? If I delete a file from one branch, will that be somehow registered in the other branch? Thanks a lot Jeeji to know if the only/easiest way to copy asourcesafe > > project including its history is to Share and Branch? > > > I am talking about a copy within the same database. > > > What bothers me with the fact that I can do it using a Share/Branch is > > that I have the feeling (I am not sure) that they still are connected > > somehow, which I do not want them to be. > > So my other question is are they connected, and what consequences can > > that possibly have? > > As long as you check "branch after share", all the files will be a new copy > branched from the old. > > --Mark
"jeeji" wrote in message news:dcccf83b-3019-432c-9516-170ea4ed277f@a1g2000hsb.googlegroups.com... > Hi and thanks for your answer > > I actually already knew that part. So what I really want to know is: > - Is that the only way of copying a project? > - If I use the Share/Branch strategy, are there any consequences. What > I mean here is are the two branches connected in a way that may have > consequences for me, if all I need in the first place is a > disconnected copy of the project? If I delete a file from one branch, > will that be somehow registered in the other branch? > > Thanks a lot > Jeeji > > to know if the only/easiest way to copy asourcesafe >> > project including its history is to Share and Branch? >> >> > I am talking about a copy within the same database. >> >> > What bothers me with the fact that I can do it using a Share/Branch is >> > that I have the feeling (I am not sure) that they still are connected >> > somehow, which I do not want them to be. >> > So my other question is are they connected, and what consequences can >> > that possibly have? >> >> As long as you check "branch after share", all the files will be a new >> copy >> branched from the old. >> >> --Mark > Deleting or purging a file, shared or branched, in one project will not affect other projects. --Mark
