Home/ Questions/Q 8278143
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T08:54:33+00:00

I have been using TortoiseSVN for a while now and just recently started using

  • 0

I have been using TortoiseSVN for a while now and just recently started using the eclipse plugin subclipse. I am really happy with it, although there is some stuff confusing me.

I have a few projects, which each have a different subfolder in the repository. I never worked with branches (so far), so my SVN use was fairly easy.

  1. Update to head
  2. Solve conflict if there are any
  3. Make some changes in the code/project
  4. Commit (Tortoise tells me, if an update is neccessary before)

Now with subclipse, I fell that there are other possibilities. For instance, what’s with the synchronize view? I don’t really get it. At the moment, I use Team->Update to head/Commit on the project folder and if there are conflicts, I use Team->Edit conflicts... on the conflicted file. That’s it. So I never touch the synchronize stuff. I haven’t really found a good explanation on the subclise page or google…

Is the idea to just synchronize and everything is done automatically or what?

Basically, I am asking for the workflow (or some link to a good basic explanation). I am not asking, what is possible or what does what, but how subclipse is intended to be used for small projects (<100 files, <5 persons working on it, no branches so far).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I do not think there is any reason to use the Synchronize view if you do not want to. I really like just doing Team > Update and then resolve whatever conflicts occur. That is much more the “SVN-way” to do it. The Synchronize view comes from Eclipse world, so Subclipse had to support it.

    TortoiseSVN does have an option that is kind of/sort of like the Synchronize view. It is the “Check for Modifications” option. Particularly when you press the “Check Repository” button.

    Also, keep in mind that the Synchronize view does not show “conflicts” the same way as SVN. In SVN, a conflict means that it could not auto-merge the change in to your file. In the Synchronize view, it means you have local modifications to a file that has incoming changes. It is possible, perhaps even likely, that SVN could automatically merge those changes if you just did an update. Personally, I would rather just let SVN try to do it.

    • 0