Projects/Related/Subversion - Revision history

Odysseus at 14:10, 1 March 2011

2011-03-01T14:10:39Z

Tampakrap: one more potential candidate for svn issue voting

2008-01-07T15:25:45Z

one more potential candidate for svn issue voting

Josef: SVN buglist to report upstream

2008-01-02T18:46:23Z

SVN buglist to report upstream

New page

SVN is great, and KDE uses it as its primary source control system, although some use SVK on top of it or switch to git to gain distributed development capabilities. SVK is slow and contains some strange branching bugs, while git requires a different development methodology - therefore, let's assume that we're going to stay with SVN for quite a while.
In light of these prospects, we should collect nasty SVN bugs to make the tool as good as possible. If we ever switch, we should then collect $SCM_OF_THE_WEEK bugs.

* svn move: The SVN server sometimes chokes on that.
* svn move: slow when moving large directories.
* svn:externals: not possible on file level.
* svn:externals: not possible for relative externals, i.e. not possible to use with different protocols.

← Older revision		Revision as of 14:10, 1 March 2011
Line 1:		Line 1:
		+	{{warning\|This page is yet to be reviewed for changes required by the migration to Git. Information and commands on this page may no longer be valid and should be used with care. Please see the [[Development/Git\|KDE Git hub page]] for more details. }}
		+
	SVN is great, and KDE uses it as its primary source control system, although some use SVK on top of it or switch to git to gain distributed development capabilities. SVK is slow and contains some strange branching bugs, while git requires a different development methodology - therefore, let's assume that we're going to stay with SVN for quite a while.		SVN is great, and KDE uses it as its primary source control system, although some use SVK on top of it or switch to git to gain distributed development capabilities. SVK is slow and contains some strange branching bugs, while git requires a different development methodology - therefore, let's assume that we're going to stay with SVN for quite a while.
	In light of these prospects, we should collect nasty SVN bugs to make the tool as good as possible. If we ever switch, we should then collect $SCM_OF_THE_WEEK bugs.		In light of these prospects, we should collect nasty SVN bugs to make the tool as good as possible. If we ever switch, we should then collect $SCM_OF_THE_WEEK bugs.

← Older revision		Revision as of 15:25, 7 January 2008
Line 6:		Line 6:
	* svn:externals: not possible on file level.		* svn:externals: not possible on file level.
	* svn:externals: not possible for relative externals, i.e. not possible to use with different protocols.		* svn:externals: not possible for relative externals, i.e. not possible to use with different protocols.
		+	* svn commit: tells that checkout is out of date only after attempt to commit when local svn properties have changed