Workflow: Using binary document formats in Git without locks (moving from subversion)

We’re a software consultancy with a multitude of projects for different customers. We traditionally use Subversion, but are currently considering moving to Git.

How can I clone an svn repository that changed layouts with git maintaining full history?

Problem I want to clone an svn repo with git-svn. The problem is the subversion repository changed layouts at r1235. Specifics From revision 1 to 1234, foo used the standard svn folder layout with: /trunk/src /tags/version/src At revision 1235, the author added bar to the repo. To do so they restructured the master repository making […]

Perforce workflow

So, we have just migrated from SVN to Perforce.

Shouldn’t SVN warn me if I’m about to commit files which have newer versions in the repository?

We use SVN and PhpStorm at work. Recently our team has grown a bit so there are several people working on the same project at a time, sometimes on the same file. We’ve run into the problem where people don’t update before comitting and overwrite the changes that were made by someone else. This is a hassle. I don’t know SVN very well, but it seems like this shouldn’t even be possible. What are we doing wrong?

Managing an undercover SVN repository

The project I am working on is version controlled by SVN, and the unspoken rule at work is to commit only when a new stable feature is added (in order to have a “clean” revision history with no revert) so I work sometimes for a few days without commiting.

Is it possible to integrate MS Project Server with SVN

We have been using Hosted SVN + Fogbugz for our source control and task/issue tracking. Our developers are very comfortable with SVN and we are hesitant to switch source control (e.g. TFS) providers at this point. However, Management extensively uses Microsoft Project for project management and are considering setting up MS Project Server.

Distributed SVN via file transfer?

I work for a large bureaucratic (and security paranoid) organisation that provides SVN for its development teams to use.

svndumpfilter Multiple Versions

I have a few questions about the Subversion open source project. I know that there are multiple versions of svndumpfilter (2,3). What are the tradeoffs and benefits of each version? In other words, what problems does each version seek to address?

Maintaining SVN history for a file when merge is done from the dev branch to trunk?

In my org, we use SVN for version control So for each build (done periodically), we merge the code to trunk from the development branch (all the developers checks in to this branch). So when we want a new branch say for a new release, we create from the trunk doing a svn copy.

What is the proper aproach of Subversion when using DLL

Background:
Our team develops a solution and it includes a number of projects. Most of the projects are built as DLLs and those DLLs are used by the rest of the projects.