On 4 April 2012 20:07, Dave Reed <dreed_at_cmal.com> wrote:
> I committed a file after deleting a line of code.
> On another machine I then updated the same file.
> But, instead of replacing the file with the latest revision, a merge was performed -- without asking me. This merge kept in place the line of code I was trying to delete.
The fact that it merged instead of replacing means that the file on
the second machine already had local changes at the time you did the
update, so it had to merge the changes bright about by the update with
the ones already made locally.
But there is no logical reason why the deletion of a line would not be
included as part of that merge. If that change were in a part of the
code modified locally then you would have seen a conflict on merging.
You need to do a diff of the file on machine 2 to see if the deleted
line has been put back in somehow. And maybe you should look at the
log for that file and diff the change that you committed. Maybe it
didn't really include the deletion you thought you had made, e.g. the
file wasn't saved before making the commit.
Sorry if that sounds really obvious, but the situation you describe
just doesn't happen normally with Subversion - it would be completely
useless as a revision control system if it did - so it looks like
something else has happened which you've not told us about, were not
aware of, or someone else did without telling you.
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-04-04 23:59:52 CEST