Subversion Repository: HOWTO - Revision history

Geneb at 19:42, 27 January 2022

2022-01-27T19:42:13Z

2009-08-26T10:52:02Z

Important notice re: change of domain.

2009-08-21T14:55:05Z

Walkthrough: Yet another broken link termina...updated.

2009-08-21T14:53:12Z

Checking Out: Terminating broken links... I'll be back

2009-04-05T20:46:52Z

Acquiring rights to commit

2009-04-05T20:44:48Z

Walkthrough

2009-04-04T09:07:19Z

Acquiring rights to commit

2009-03-29T15:59:10Z

Walkthrough

2009-03-23T15:14:03Z

Walkthrough

2009-03-20T08:30:06Z

Walkthrough: Trying to get people *not* to put a commit message on the command line.

← Older revision		Revision as of 19:42, 27 January 2022
Line 1:		Line 1:
		+	'''NOTE THAT THIS HOWTO NO LONGER APPLIES - IT'S AVAILABLE FOR HISTORICAL REASONS ONLY'''
		+
	'''Important notice''': if you have checked out from gpl.openqm.com (as many people will have) you will need to update your Subversion repository to point to the ScarletDME domain instead. You can do this with the following command, executed at the root of your working copy:		'''Important notice''': if you have checked out from gpl.openqm.com (as many people will have) you will need to update your Subversion repository to point to the ScarletDME domain instead. You can do this with the following command, executed at the root of your working copy:
	<nowiki> svn switch --relocate https://gpl.openqm.com https://scarletdme.org </nowiki>		<nowiki> svn switch --relocate https://gpl.openqm.com https://scarletdme.org </nowiki>

← Older revision		Revision as of 10:52, 26 August 2009
Line 1:		Line 1:
		+	'''Important notice''': if you have checked out from gpl.openqm.com (as many people will have) you will need to update your Subversion repository to point to the ScarletDME domain instead. You can do this with the following command, executed at the root of your working copy:
		+	<nowiki> svn switch --relocate https://gpl.openqm.com https://scarletdme.org </nowiki>
		+	You can also do this from a GUI such as TortoiseSVN, but you '''must''' use the 'relocate' option; the standard 'switch' command is different and is described below.
		+
	== Introduction ==		== Introduction ==

@@ Line 44: / Line 44: @@
 If you just made the working directory then use svn checkout to get a copy of the project (all branches, tags and trunk of project openqm in this example)
-  svn checkout https://gpl.openqm.com/svn/qmvdb/openqm
+  svn checkout https://www.scarletdme.org/svn/qmvdb/openqm
 OR, if you already checked out a copy of the repo, then best to ensure you are working on the latest version to avoid later work resolving any conflicts with other people's edits.

@@ Line 164: / Line 164: @@
 Fill in the details
-URL? https://gpl.openqm.com/svn/qmvdb
+URL? https://www.scarletdme.org/svn/qmvdb
 Checkout Folder? D:\Documents and settings\steve\Desktop\TESTIT

← Older revision		Revision as of 20:46, 5 April 2009
Line 21:		Line 21:

	htpasswd /etc/subversion/passwd yourdesiredusername		htpasswd /etc/subversion/passwd yourdesiredusername
		+
		+	Then commit with something like the following. username is usually cached and only required the first time.
		+
		+	svn --username yourdesiredusername commit

	== Command Line User Interface ==		== Command Line User Interface ==

@@ Line 110: / Line 110: @@
 Commit your changes WITH A CONCISE COMMENT ABOUT ITS PURPOSE so people can get a good idea by looking at the log.  This is so important that if you don't include a log message, Subversion will ask you for one.  It is suggested that you do ''not'' include a message on the command line, so you can use the editor of your choice to write the message.   The key advantage to this (other than being able to write multiline comments more easily) is that it shows you *exactly* which files it's going to commit (along with why, if you can read the codes).  If you've forgotten something, or are commiting something you didn't mean to, you can just quit the editor and Subversion will ask you if you want to quit.  It helps to avoid unnecessary commits and embarrassing log comments.  To commit using this method, use
   svn commit trunk/gplsrc/dh_ak.c
 or, to write your message on the command line,
   svn commit -m "Bug fix for indexing on complex fields in non-VERSION 1 files from MP in Sep08 via AC"
 If you made an edit to a file and then backed out the change, you can easily revert back to the svn version of the file using "revert":

@@ Line 18: / Line 18: @@
   htpasswd -n yourdesiredusername
-then any admin (with root or sudo access) can grant user xxxxxxxxx access with the following command. It will ask for the password which is hashed password after the : in the output of the above/previous htpasswd command.
+then any gpl.openqm.com server admin (with root or sudo access) can grant user yourdesiredusername access with the following command. It will ask for the password which is hashed password after the : in the output of the above/previous htpasswd command.
-  htpasswd /etc/subversion/passwd xxxxxxxxx
+  htpasswd /etc/subversion/passwd yourdesiredusername
 == Command Line User Interface ==