Developers - Revision history

Pfournier: Migration of the revision control system to Git.

2009-08-07T17:29:57Z

Migration of the revision control system to Git.

← Older revision		Revision as of 17:29, 7 August 2009
Line 11:		Line 11:
	The HylaFAX developers list is a subscriber-only list. You must subscribe before posting.		The HylaFAX developers list is a subscriber-only list. You must subscribe before posting.

	==~~CVS~~==		==Git==

	HylaFAX development is controlled by ~~CVS~~. Read-access is open to all, although write access is not. Unless you're doing a large amount of coding, it is suggested that you post proposed patches and explanations of them on the hylafax-devel mailing list.		HylaFAX development is controlled by Git. Read-access is open to all, although write access is not. Unless you're doing a large amount of coding, it is suggested that you post proposed patches and explanations of them on the hylafax-devel mailing list.

	HylaFAX is currently being maintained on a public ~~CVS~~ server. An up to date copy of the hylafax source tree can be easily obtained by accessing the server as follows:		HylaFAX is currently being maintained on a public Git server. An up to date copy of the hylafax source tree can be easily obtained by accessing the server as follows:

	<pre>		<pre>

	* Browsing:		* Browsing:

	The latest source code changes can be viewed at anytime from the following ~~urls~~:		The latest source code changes can be viewed at anytime from the following url:

	http://git.hylafax.org/HylaFAX		http://git.hylafax.org/HylaFAX

	~~http://www.hylafax.org/viewvc/hylafax/~~

	* Downloading:		* Downloading:

	To do this you need to:		To do this you need to:
	1. Grab a recent copy of the ~~cvs~~ software(client software is sufficient). Many		1. Grab a recent copy of the Git software(client software is sufficient). Many
	UNIX distributions include ~~cvs~~, and the latest version can always be obtained		UNIX distributions include git, and the latest version can always be obtained
	from:		from:

	http://~~www~~.~~nongnu.org/cvs~~/		http://git-scm.com/

	~~2. Set the CVSROOT environment variable to~~

	~~:pserver:cvs@cvs.hylafax.org:/cvsroot~~

	~~3. Run the command:~~

	~~cvs login~~

	~~Enter the password string which is simply "cvs"~~

	4. To checkout the distribution, run the command:		2. To checkout the distribution, run the command:

	~~cvs co~~ hylafax		git clone git://git.hylafax.org/HylaFAX

	5. Whenever you want to merge with the latest code changes:		3. Whenever you want to merge with the latest code changes:

	~~cvs update -d -P~~		git pull

	* Commands:		* Commands:

	Some ~~cvs~~ commands that may be of use:		Some Git commands that may be of use:

	~~login login~~ to ~~the cvs server~~		checkout change to a different branch
	~~get/checkout downloads~~ a ~~local copy of the requested module~~		pull bring your working directory up to date with the repository
	~~update~~ bring your ~~wrking~~ directory up to ~~datec~~ with the repository		add adds a new file or changes to existing files to your local repository
	add adds a new file to ~~the repositroy, requires write access~~		commit apply (added) changes to your local repository
	commit apply ~~local~~ changes to ~~the repositroy, requires write access~~
	diff shows differences between local files and repository		diff shows differences between local files and repository
	~~history shows reports on commands against the cvs repository~~		log shows Git log information
	log shows ~~cvs~~ log information		status shows the working tree status
	~~rdiff used to prepare a diff file between releases~~		rebase forward-port local commits to the updated upstream head
	status shows ~~current~~ status ~~if files in repository and~~ local ~~copies~~		tag applies a tag to your local repository
	tag applies a tag to ~~the~~ repository, requires write access		push push local commits to official repository, requires write access
	</pre>		</pre>

	==Beta Versions of HylaFAX==		==Beta Versions of HylaFAX==
	The latest information on [[Beta Versions\|HylaFAX beta versions]].		The latest information on [[Beta Versions\|HylaFAX beta versions]].

Admin: /* CVS */

2007-10-03T05:22:07Z

CVS

← Older revision		Revision as of 05:22, 3 October 2007
Line 21:		Line 21:
	* Browsing:		* Browsing:

	The latest source code changes can be viewed at anytime from the following ~~url~~:		The latest source code changes can be viewed at anytime from the following urls:

			http://git.hylafax.org/HylaFAX

	http://www.hylafax.org/viewvc/hylafax/		http://www.hylafax.org/viewvc/hylafax/

Darren: /* CVS */

2006-09-03T23:39:56Z

CVS

← Older revision		Revision as of 23:39, 3 September 2006
Line 28:		Line 28:

	To do this you need to:		To do this you need to:
	1. Grab a recent copy of the cvs software(client software is sufficient). ~~The~~		1. Grab a recent copy of the cvs software(client software is sufficient). Many
	latest version can be obtained from ~~the cyclic website~~:		UNIX distributions include cvs, and the latest version can always be obtained
			from:

	http://www.~~cyclic~~.~~com~~/		http://www.nongnu.org/cvs/

	2. Set the CVSROOT environment variable to		2. Set the CVSROOT environment variable to

Darren: /* CVS */

2006-04-22T17:04:54Z

CVS

← Older revision		Revision as of 17:04, 22 April 2006
Line 23:		Line 23:
	The latest source code changes can be viewed at anytime from the following url:		The latest source code changes can be viewed at anytime from the following url:

	http://www.hylafax.org/~~cgi-bin~~/~~cvsweb.cgi~~		http://www.hylafax.org/viewvc/hylafax/

	* Downloading:		* Downloading:

Paul at 19:55, 12 January 2006

2006-01-12T19:55:24Z

← Older revision		Revision as of 19:55, 12 January 2006
Line 67:		Line 67:
	tag applies a tag to the repository, requires write access		tag applies a tag to the repository, requires write access
	</pre>		</pre>

			==Beta Versions of HylaFAX==
			The latest information on [[Beta Versions\|HylaFAX beta versions]].

Admin: /* Reporting Bugs */

2005-12-19T16:37:11Z

Reporting Bugs

← Older revision		Revision as of 16:37, 19 December 2005
Line 3:		Line 3:
	==Reporting Bugs==		==Reporting Bugs==

	Faithful to our open-source bias, ~~HylaFAX™~~ bugs are tracked using [http://www.mozilla.org/projects/bugzilla/ Bugzilla], a product of the [http://www.mozilla.org/ Mozilla Project]. Please do your best to make sure you've really found a bug, and then file it on the HylaFAX Bugzilla, located at [http://bugs.hylafax.org/ http://bugs.hylafax.org/]. To confirm a bug one should first check the mailing list archives for other reports of this issue (and possible resolution) and then post to the developers mailing list (described above). Security-related bugs should be reported to security@hylafax.org in order to avoid exploitation of the problem before it can be publicly resolved.		Faithful to our open-source bias, HylaFAX bugs are tracked using [http://www.mozilla.org/projects/bugzilla/ Bugzilla], a product of the [http://www.mozilla.org/ Mozilla Project]. Please do your best to make sure you've really found a bug, and then file it on the HylaFAX Bugzilla, located at [http://bugs.hylafax.org/ http://bugs.hylafax.org/]. To confirm a bug one should first check the mailing list archives for other reports of this issue (and possible resolution) and then post to the developers mailing list (described above). Security-related bugs should be reported to security@hylafax.org in order to avoid exploitation of the problem before it can be publicly resolved.

	==Developer Mailing List==		==Developer Mailing List==

Admin: /* Developer Mailing List */

2005-12-19T16:36:57Z

Developer Mailing List

← Older revision		Revision as of 16:36, 19 December 2005
Line 9:		Line 9:
	For now please visit the [[Mailing Lists\|Mailing List Page]] for more information.		For now please visit the [[Mailing Lists\|Mailing List Page]] for more information.

	The ~~HylaFAX™~~ developers list is a subscriber-only list. You must subscribe before posting.		The HylaFAX developers list is a subscriber-only list. You must subscribe before posting.

	==CVS==		==CVS==

209.166.32.60: /* Developer Mailing List */

2005-12-12T04:21:55Z

Developer Mailing List

← Older revision		Revision as of 04:21, 12 December 2005
Line 9:		Line 9:
	For now please visit the [[Mailing Lists\|Mailing List Page]] for more information.		For now please visit the [[Mailing Lists\|Mailing List Page]] for more information.

	The HylaFAX™ developers list is a subscriber-only list. You must subscribe ~~first~~ before posting.		The HylaFAX™ developers list is a subscriber-only list. You must subscribe before posting.

	==CVS==		==CVS==

209.166.32.60: /* CVS */

2005-12-12T04:21:17Z

CVS

← Older revision		Revision as of 04:21, 12 December 2005
Line 28:		Line 28:

	To do this you need to:		To do this you need to:
	1. Grab a recent copy of the cvs software(client software is sufficient). The latest version can be obtained from the cyclic website:		1. Grab a recent copy of the cvs software(client software is sufficient). The
			latest version can be obtained from the cyclic website:

	http://www.cyclic.com/		http://www.cyclic.com/

Admin at 17:13, 7 December 2005

2005-12-07T17:13:39Z

← Older revision		Revision as of 17:13, 7 December 2005
Line 1:		Line 1:
	The HylaFAX developer community is always looking for new recruits. Don't be scared, you're welcome to lurk until you feel comfortable! If you're looking to become involved on any level, you should definitely subscribe to to the [~~http://www.hylafax.org/mailing-lists.html~~ hylafax developers mailing list].		The HylaFAX developer community is always looking for new recruits. Don't be scared, you're welcome to lurk until you feel comfortable! If you're looking to become involved on any level, you should definitely subscribe to to the [[Mailing Lists\|hylafax developers mailing list]].

	~~The HylaFAX™ developers list is a subscriber-only list. You must subscribe first before posting.~~		==Reporting Bugs==

	'~~''Reporting Bugs'''~~		Faithful to our open-source bias, HylaFAX™ bugs are tracked using [http://www.mozilla.org/projects/bugzilla/ Bugzilla], a product of the [http://www.mozilla.org/ Mozilla Project]. Please do your best to make sure you've really found a bug, and then file it on the HylaFAX Bugzilla, located at [http://bugs.hylafax.org/ http://bugs.hylafax.org/]. To confirm a bug one should first check the mailing list archives for other reports of this issue (and possible resolution) and then post to the developers mailing list (described above). Security-related bugs should be reported to security@hylafax.org in order to avoid exploitation of the problem before it can be publicly resolved.

			==Developer Mailing List==

			For now please visit the [[Mailing Lists\|Mailing List Page]] for more information.

	~~Faithful to our open-source bias,~~ HylaFAX™ bugs are tracked using [http://www.mozilla.org/projects/bugzilla/ Bugzilla], a product of the [http://www.mozilla.org/ Mozilla Project]. Please do your best to make sure you've really found a bug, and then file it on the HylaFAX Bugzilla, located at [http://bugs.hylafax.org/ http://bugs.hylafax.org/]. To confirm a bug one should first check the mailing list archives for other reports of this issue (and possible resolution) and then post to the developers ~~mailing~~ list ~~(described above). Security~~-~~related bugs should be reported to security@hylafax~~.~~org in order to avoid exploitation of the problem~~ before ~~it can be publicly resolved~~.		The HylaFAX™ developers list is a subscriber-only list. You must subscribe first before posting.

	~~'''~~CVS~~'''~~		==CVS==

	HylaFAX development is controlled by CVS. Read-access is open to all, although write access is not. Unless you're doing a large amount of coding, it is suggested that you post proposed patches and explanations of them on the hylafax-devel mailing list.		HylaFAX development is controlled by CVS. Read-access is open to all, although write access is not. Unless you're doing a large amount of coding, it is suggested that you post proposed patches and explanations of them on the hylafax-devel mailing list.