darcs:intro
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
darcs:intro [2011/10/22 12:50] – LaweqmXLygtYQDvym 193.147.24.4 | darcs:intro [2018/06/23 00:30] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | d5XTtA , [url=http://tmazmypveobf.com/]tmazmypveobf[/url], [link=http://tcsjwmidrydx.com/]tcsjwmidrydx[/link], http://ukzyzetxwddm.com/ | + | ====== CobraMUSH Darcs Repositories ====== |
+ | [[:About | CobraMUSH]] source code in development utilizes [[darcs> | Darcs]] for its Revision Control System. | ||
+ | |||
+ | The CobraMUSH repositories where all development takes place are browsable at http://darcs.cobramush.org. | ||
+ | |||
+ | ====== Darcs for CobraMUSH developers ====== | ||
+ | A guide to getting started with Darcs Revision Control System is located [[Darcs> | ||
+ | |||
+ | ===== How to grab a copy of CobraMUSH ===== | ||
+ | The recommended way to grab your copy of darcs is using the --set-scripts-executable switch, since the CobraMUSH project contains many scripts that need to be set in order for the [[:About | CobraMUSH]] distribution to work. | ||
+ | darcs get http:// | ||
+ | |||
+ | where < | ||
+ | darcs get http:// | ||
+ | darcs get http:// | ||
+ | |||
+ | Then cd into the cobramush directory and run: | ||
+ | sh utils/ | ||
+ | |||
+ | This script requires that you have the ' | ||
+ | |||
+ | ===== Keep your repository up to date ===== | ||
+ | Darcs is a simple push/pull system of patches. | ||
+ | cd my_local_cobramush_repoistory | ||
+ | darcs pull | ||
+ | |||
+ | This will in turn pull patch by patch asking you if you want to apply them out of all the recorded pushed patches in that particular | ||
+ | |||
+ | ===== Record changes to your checked out repository ===== | ||
+ | To record changes to your checked out CobraMUSH repository. | ||
+ | |||
+ | When you have reached the point you would like to record all the specific changes to a particular darcs patch, simply type: | ||
+ | darcs record | ||
+ | When the darcs record command initiated, it will go through all the changes made in your checked out repoistory similar to a patchfiles showing hunk by hunk so you may pick which changes in particular you would like to record to the particular darcs patch you are making. | ||
+ | |||
+ | ===== How to send changes to the CobraMUSH Repoistory ===== | ||
+ | Depending on what kinda access you as the developer have. You may or may not have direct push access to the repoistory. If you do, most likely [[people: | ||
+ | |||
+ | ==== Using Darcs Push ==== | ||
+ | The push command darcs is the most commonly documented way to push changes to a Darcs Repoistory. | ||
+ | by the following command. | ||
+ | darcs push | ||
+ | or if your pushing to another repoistory, for the instance your sending a change to the stable and development repoistories. | ||
+ | darcs push <path to darcs repoistory> | ||
+ | A typical instance of using the darcs push command is shown below. | ||
+ | [cobramush@nveid[ttypts/10]~/darcs_sources/ | ||
+ | |||
+ | Mon Sep 4 22:23:49 EDT 2006 Ari Johnson | ||
+ | * Updated repository for 0.73 development | ||
+ | Shall I push this patch? (1/ | ||
+ | |||
+ | Tue Sep 5 12:42:46 EDT 2006 Ari Johnson | ||
+ | * Changed connect.txt version number | ||
+ | Shall I push this patch? (2/8) [ynWvpxqadjk], or ? for help: n | ||
+ | |||
+ | Fri Oct 6 20:17:02 EDT 2006 Nveid | ||
+ | * cobrachathooks - necesarry hooks inside cobramush for the new beta cobra | ||
+ | chat system. | ||
+ | Shall I push this patch? (6/8) [ynWvpxqadjk], | ||
+ | |||
+ | Sat Oct 7 01:49:42 EDT 2006 Nveid | ||
+ | * cobrapluschat - added pluschattable stuff for cobrachatness. | ||
+ | Shall I push this patch? (7/8) [ynWvpxqadjk], | ||
+ | |||
+ | Sat Oct 7 13:59:16 EDT 2006 Nveid | ||
+ | * Fixed it so division quotas are checked properley when an object is added to | ||
+ | another divisions quota. | ||
+ | Shall I push this patch? (8/8) [ynWvpxqadjk], | ||
+ | Finished applying... | ||
+ | |||
+ | ==== Using Darcs Send ==== | ||
+ | Another way to send to the CobraMUSH repoistory is using the '' | ||
+ | send in your darcs patches. | ||
+ | |||
+ | Each [[: | ||
+ | |||
+ | == Valid Development Patch Email Addresses == | ||
+ | |||
+ | Note that these addresses are currently offline. | ||
+ | |||
+ | * devpatches-080@cobramush.org | ||
+ | * devpatches-073@cobramush.org | ||
+ | * devpatches-072@cobramush.org | ||
+ | |||
+ | ==== ==== | ||
+ | Sending a darcs patch is much similar to the process done using darcs push. Only instead of specifying a path, you specify the email address and you give it the --sign darcs switch. | ||
+ | darcs send --sign --to=< | ||
+ | Parties that happen to spot a bug in the CobraMUSH code, and are not an official CobraMUSH developer may contribute as well. However those such patches should be sent to the Development Team directly at [[cobramush-devteam@lists.theari.com]] where the CobraMUSH developers may review the Darcs patch sent in before applying it. |
darcs/intro.1319302224.txt.gz · Last modified: 2018/06/23 00:30 (external edit)