BerlinRoofNetRepository - Revision history

Jkm: /* Switching from old repository to the new */

2006-03-24T10:44:26Z

Switching from old repository to the new

← Older revision		Revision as of 10:44, 24 March 2006
Line 74:		Line 74:
	svn switch --relocate svn://brn-svn/brn/platform/wgt634u/brn svn://brn-svn/BerlinRoofNet/trunk/click/packages/brn/		svn switch --relocate svn://brn-svn/brn/platform/wgt634u/brn svn://brn-svn/BerlinRoofNet/trunk/click/packages/brn/
	</pre>		</pre>
			'''I read that executing "switch svn://brn-svn/BerlinRoofNet/trunk/click/packages/brn/" may be enough, but what's the difference to the above.'''
	This will relocate your working copy from svn://brn-svn/brn/platform/wgt634u/brn (copy this svn-URL from svn info's output) to svn://brn-svn/BerlinRoofNet/trunk/click/packages/brn/, which is the new place for the brn package. To find the proper place, consider using the web interface http://brn-svn.sar.informatik.hu-berlin.de to browse the repository. The structure is quite self-explaining.		This will relocate your working copy from svn://brn-svn/brn/platform/wgt634u/brn (copy this svn-URL from svn info's output) to svn://brn-svn/BerlinRoofNet/trunk/click/packages/brn/, which is the new place for the brn package. To find the proper place, consider using the web interface http://brn-svn.sar.informatik.hu-berlin.de to browse the repository. The structure is quite self-explaining.
	* Execute "svn ci" to commit you changes to the new repository.		* Execute "svn ci" to commit you changes to the new repository.
Line 81:		Line 82:
	After migrating your changes, '''you should check out the new repository and work with the new one'''. But keep in mind, that the entire repository is quite huge. Consider checking out only the sources you are working with, if you are on a slow connection or having little storage.		After migrating your changes, '''you should check out the new repository and work with the new one'''. But keep in mind, that the entire repository is quite huge. Consider checking out only the sources you are working with, if you are on a slow connection or having little storage.

	~~I'm figuring out an elegant way to~~ copy changes made to ~~the~~ ~~old~~ ~~repository~~ ~~and~~ ~~moving~~ ~~them~~ to the new ~~one.~~ ~~This~~ is ~~important~~ ~~for~~ ~~all~~ ~~changes~~ ~~made~~ ~~since revision 1981~~. ~~I think we need to merge branches~~. ~~There~~ ~~is a chapter about this in the~~ SVN book, ~~which~~ is available at http://svnbook.red-bean.com/.		To copy changes (made after revision 1981) from the old revision to the new read the chapter about "Branching and Merging" [http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.branchmerge]. The complete SVN book is available at http://svnbook.red-bean.com/.

Jkm: /* Switching from old repository to the new */

2006-03-23T15:47:24Z

Switching from old repository to the new

← Older revision		Revision as of 15:47, 23 March 2006
Line 81:		Line 81:
	After migrating your changes, '''you should check out the new repository and work with the new one'''. But keep in mind, that the entire repository is quite huge. Consider checking out only the sources you are working with, if you are on a slow connection or having little storage.		After migrating your changes, '''you should check out the new repository and work with the new one'''. But keep in mind, that the entire repository is quite huge. Consider checking out only the sources you are working with, if you are on a slow connection or having little storage.

	I'm figuring out an elegant way to copy changes made to the old repository and moving them to the new one. This is important for all changes made since revision 1981.		I'm figuring out an elegant way to copy changes made to the old repository and moving them to the new one. This is important for all changes made since revision 1981. I think we need to merge branches. There is a chapter about this in the SVN book, which is available at http://svnbook.red-bean.com/.

Jkm: /* Switching from old repository to the new */

2006-03-23T15:29:20Z

Switching from old repository to the new

← Older revision		Revision as of 15:29, 23 March 2006
Line 55:		Line 55:

	=Switching from old repository to the new=		=Switching from old repository to the new=
	'''Before we start, do a backup of your working copy. If we ~~ran~~ into problems, we may need it.'''		'''Before we start, do a backup of your working copy. If we run into problems, we may need it.'''
	If you made changes to a checked out version of BRN stuff from the old repository, the following steps should change your working copy to the new one. '''This works only for the changes you didn't commit to the old repository'''.		If you made changes to a checked out version of BRN stuff from the old repository, the following steps should change your working copy to the new one. '''This works only for the changes you didn't commit to the old repository'''.
	* Type "svn info" in your working directory.		* Type "svn info" in your working directory.

Jkm: /* Switching from old repository to the new */

2006-03-23T15:28:50Z

Switching from old repository to the new

← Older revision		Revision as of 15:28, 23 March 2006
Line 55:		Line 55:

	=Switching from old repository to the new=		=Switching from old repository to the new=
			'''Before we start, do a backup of your working copy. If we ran into problems, we may need it.'''
	If you made changes to a checked out version of BRN stuff from the old repository, the following steps should change your working copy to the new one. '''This works only for the changes you didn't commit to the old repository'''.		If you made changes to a checked out version of BRN stuff from the old repository, the following steps should change your working copy to the new one. '''This works only for the changes you didn't commit to the old repository'''.
	* Type "svn info" in your working directory.		* Type "svn info" in your working directory.

Jkm: /* Switching from old repository to the new */

2006-03-23T15:23:35Z

Switching from old repository to the new

← Older revision		Revision as of 15:23, 23 March 2006
Line 80:		Line 80:
	After migrating your changes, '''you should check out the new repository and work with the new one'''. But keep in mind, that the entire repository is quite huge. Consider checking out only the sources you are working with, if you are on a slow connection or having little storage.		After migrating your changes, '''you should check out the new repository and work with the new one'''. But keep in mind, that the entire repository is quite huge. Consider checking out only the sources you are working with, if you are on a slow connection or having little storage.

	I'm figuring out a way to copy changes made to the old repository and moving them to the new. This is important for all changes made since revision 1981.		I'm figuring out an elegant way to copy changes made to the old repository and moving them to the new one. This is important for all changes made since revision 1981.

Jkm: /* Switching from old repository to the new */

2006-03-23T15:21:22Z

Switching from old repository to the new

← Older revision		Revision as of 15:21, 23 March 2006
Line 55:		Line 55:

	=Switching from old repository to the new=		=Switching from old repository to the new=
	If you made changes to a checked out version of BRN stuff from the old repository, the following steps should change your working copy to the new one:		If you made changes to a checked out version of BRN stuff from the old repository, the following steps should change your working copy to the new one. '''This works only for the changes you didn't commit to the old repository'''.
	* Type "svn info" in your working directory.		* Type "svn info" in your working directory.
	<pre>		<pre>
Line 79:		Line 79:

	After migrating your changes, '''you should check out the new repository and work with the new one'''. But keep in mind, that the entire repository is quite huge. Consider checking out only the sources you are working with, if you are on a slow connection or having little storage.		After migrating your changes, '''you should check out the new repository and work with the new one'''. But keep in mind, that the entire repository is quite huge. Consider checking out only the sources you are working with, if you are on a slow connection or having little storage.

			I'm figuring out a way to copy changes made to the old repository and moving them to the new. This is important for all changes made since revision 1981.

Jkm: /* Switching from old repository to the new */

2006-03-23T15:07:09Z

Switching from old repository to the new

← Older revision		Revision as of 15:07, 23 March 2006
Line 78:		Line 78:
	This way you can check in all the changes you made to your "old" working copy.		This way you can check in all the changes you made to your "old" working copy.

	After migrating your changes, '''you should check out the new repository and work with the new one'''.		After migrating your changes, '''you should check out the new repository and work with the new one'''. But keep in mind, that the entire repository is quite huge. Consider checking out only the sources you are working with, if you are on a slow connection or having little storage.

Jkm: /* Switching from old repository to the new */

2006-03-23T15:02:27Z

Switching from old repository to the new

← Older revision		Revision as of 15:02, 23 March 2006
Line 78:		Line 78:
	This way you can check in all the changes you made to your "old" working copy.		This way you can check in all the changes you made to your "old" working copy.

	After ~~all~~ it is ~~strongly~~ ~~encouraged~~ to ~~switch to~~ the new repository, ~~after~~ ~~checking~~ in ~~your~~ ~~sources~~.		After migrating your changes, '''you should check out the new repository and work with the new one'''.

Jkm: /* Switching from old repository to the new */

2006-03-23T14:59:55Z

Switching from old repository to the new

← Older revision		Revision as of 14:59, 23 March 2006
Line 76:		Line 76:
	* Execute "svn ci" to commit you changes to the new repository.		* Execute "svn ci" to commit you changes to the new repository.

	This way you can check in all the changes you made to your old working copy.		This way you can check in all the changes you made to your "old" working copy.

	After all it is strongly encouraged to switch to the new repository, after checking in your sources.		After all it is strongly encouraged to switch to the new repository, after checking in your sources.

Jkm: /* Switching from old repository to the new */

2006-03-23T14:59:33Z

Switching from old repository to the new

← Older revision		Revision as of 14:59, 23 March 2006
Line 73:		Line 73:
	svn switch --relocate svn://brn-svn/brn/platform/wgt634u/brn svn://brn-svn/BerlinRoofNet/trunk/click/packages/brn/		svn switch --relocate svn://brn-svn/brn/platform/wgt634u/brn svn://brn-svn/BerlinRoofNet/trunk/click/packages/brn/
	</pre>		</pre>
	This will relocate your working copy from svn://brn-svn/brn/platform/wgt634u/brn to svn://brn-svn/BerlinRoofNet/trunk/click/packages/brn/, which is the new place for the brn package. To find the proper place, consider using the web interface http://brn-svn.sar.informatik.hu-berlin.de to browse the repository. The structure is quite self-explaining.		This will relocate your working copy from svn://brn-svn/brn/platform/wgt634u/brn (copy this svn-URL from svn info's output) to svn://brn-svn/BerlinRoofNet/trunk/click/packages/brn/, which is the new place for the brn package. To find the proper place, consider using the web interface http://brn-svn.sar.informatik.hu-berlin.de to browse the repository. The structure is quite self-explaining.
	* Execute "svn ci" to commit you changes to the new repository.		* Execute "svn ci" to commit you changes to the new repository.

			This way you can check in all the changes you made to your old working copy.

			After all it is strongly encouraged to switch to the new repository, after checking in your sources.