Working with SVN - Revision history

⚠️NikosA: Category:MoveToTrac

2013-02-09T10:30:48Z

Category:MoveToTrac

← Older revision		Revision as of 10:30, 9 February 2013
Line 1:		Line 1:
			{{MoveToTrac}}


	[''I find the main GRASS website SVN help pages many, complex, and confusing. So trying to start over here with a more concise help page'']		[''I find the main GRASS website SVN help pages many, complex, and confusing. So trying to start over here with a more concise help page'']

Neteler: first bunch of updates

2009-02-10T10:50:21Z

first bunch of updates

Show changes

⚠️HamishBowman: /* Getting help */ irc link

2009-02-09T23:24:31Z

Getting help: irc link

← Older revision		Revision as of 23:24, 9 February 2009
Line 187:		Line 187:
	==== Getting help ====		==== Getting help ====

	* IRC		* [http://grass.osgeo.org/community/support.php#irc IRC] - Internet Relay Chat
	* [http://grass.ibiblio.org/devel/index.php#list GRASS-dev mailing list]		* [http://grass.ibiblio.org/devel/index.php#list GRASS-dev mailing list]

⚠️HamishBowman: /* Preparing a patch */ updates

2009-02-09T23:18:58Z

Preparing a patch: updates

← Older revision		Revision as of 23:18, 9 February 2009
Line 144:		Line 144:
	==== Preparing a patch ====		==== Preparing a patch ====

	* ~~create a unidiff patch against~~ the ~~latest development branch CVS~~		* ''See the wiki page describing [[Patches]].''

	Be sure to create unified ("diff -u") format. "Plain" diffs (the default		* Create a Unidiff patch against the latest development branch SVN (trunk).
	format) are risky, because they will apply without warning to code which
	has been substantially changed; they are also harder to read than unified.		Be sure to create them in unified ("diff -u") format. "Plain" diffs (the default format) are risky, because they will apply without warning to code which has been substantially changed; they are also harder to read than unified. The default for '<tt>svn diff</tt>' is to create a unidiff.

	Such diffs should be made from the top-level directory, e.g.		Such diffs should be made from the top-level directory, e.g.
	"~~cvs~~ diff -u display/d.vect/main.c"; that way, the diff will		"<tt>svn diff display/d.vect/main.c</tt>"; that way, the diff will include the pathname rather than just the generic "main.c".
	include the pathname rather than just "main.c".

	Imagine, that You have hacked around in module r.foo. To create patch~~, You~~ should use following commands:		Imagine that You have hacked around in module r.foo. To create a patch you should use following commands:
	cd /path/to/grass6		cd /path/to/grass6
	~~cvs~~ diff -u raster/r.foo > r.foo.patch		svn diff raster/r.foo > r.foo.patch

	==== Applying someone else patch ====		==== Applying someone else patch ====

⚠️HamishBowman: /* Creating a GEM package */

2008-10-11T01:44:06Z

Creating a GEM package

← Older revision		Revision as of 01:44, 11 October 2008
Line 168:		Line 168:
	The GEM system makes it easy to prepare intergrated add-on modules or groups of add-on modules as extensions to the existing GRASS source code. Users do not need to build the entire GRASS source package to add and build GEM packages.		The GEM system makes it easy to prepare intergrated add-on modules or groups of add-on modules as extensions to the existing GRASS source code. Users do not need to build the entire GRASS source package to add and build GEM packages.

	* ~~link to GEM add-on docs~~		* {{cmd\|gem/index}} documentation

	==== Submitting it to the Wiki Add-Ons page ====		==== Submitting it to the Wiki Add-Ons page ====

⚠️HamishBowman: Working with CVS moved to Working with SVN: stumbling into the future

2008-10-11T01:41:49Z

Working with CVS moved to Working with SVN: stumbling into the future

← Older revision		Revision as of 01:41, 11 October 2008
(No difference)

⚠️Landa: +category development

2008-04-12T23:55:57Z

+category development

← Older revision		Revision as of 23:55, 12 April 2008
Line 223:		Line 223:
	* cvs commit: make the cvs log message a useful synopsis of the change		* cvs commit: make the cvs log message a useful synopsis of the change
	* double check the change using the live WebCVS interface or [http://grass.itc.it/mailman/listinfo/grass-commit grass-commit mailing list]		* double check the change using the live WebCVS interface or [http://grass.itc.it/mailman/listinfo/grass-commit grass-commit mailing list]

			[[Category:Development]]

⚠️HamishBowman: /* What are branches and tags? */ typo

2007-12-13T07:12:04Z

What are branches and tags?: typo

← Older revision		Revision as of 07:12, 13 December 2007
Line 9:		Line 9:
	=== What are branches and tags? ===		=== What are branches and tags? ===

	CVS (the collaborative ~~souce~~ code repository and tracking system we use) is broken down into three distinct parts: repositories, branches, and tags.		CVS (the collaborative source code repository and tracking system we use) is broken down into three distinct parts: repositories, branches, and tags.

	1. '''repository'''. contains all source code and history for a project. aka ''HEAD''		1. '''repository'''. contains all source code and history for a project. aka ''HEAD''

⚠️HamishBowman: /* CVS/SVN Overview */

2007-12-13T07:08:15Z

CVS/SVN Overview

← Older revision		Revision as of 07:08, 13 December 2007
Line 20:		Line 20:
	: for example ''release_20071127_grass_6_2_3'' in the ''releasebranch_6_2'' branch for the GRASS 6.2.3 release		: for example ''release_20071127_grass_6_2_3'' in the ''releasebranch_6_2'' branch for the GRASS 6.2.3 release

			=== Implementation ===

	The general principle is that no development occurs on a release		The general principle is that no development occurs on a release

⚠️HamishBowman: /* CVS/SVN Overview */

2007-12-13T07:02:52Z

CVS/SVN Overview

← Older revision		Revision as of 07:02, 13 December 2007
Line 3:		Line 3:
	== CVS/SVN Overview ==		== CVS/SVN Overview ==

	Collaborative source code management using CVS or SVN contains a trunk (aka HEAD), branches, and tags.		Collaborative source code management using CVS or Subversion (SVN) keeps track of source code changes in a central spot and handles all the accounting work needed to cleanly handle version numbers and change history.

			A CVS/SVN repository contains a trunk (aka HEAD), branches, and tags.

	=== What are branches and tags? ===		=== What are branches and tags? ===