Fulltext results:

reference @script

10 Hits, Last modified: 4 years ago

* [[https://git.skyjake.fi/doomsday/engine/src/branch/master/doomsday/sdk/libcore/net.dengine.stdlib.pack/modu... * [[https://git.skyjake.fi/doomsday/engine/src/branch/master/doomsday/apps/client/net.dengine.client.pack/modu... * [[https://git.skyjake.fi/doomsday/engine/src/branch/master/doomsday/apps/client/net.dengine.client.pack/modu... /git.skyjake.fi/doomsday/skyjake.doomsdaylang/src/branch/master/syntaxes|Syntax definitions in TextMate format]]

clientconfig @script:module

2 Hits, Last modified: 5 years ago

**. [[https://git.skyjake.fi/doomsday/engine/src/branch/master/doomsday/apps/client/net.dengine.client.pack/modu

roadmap @devel

17 Hits, Last modified: 6 years ago

ug fixing in other parts of the code. To keep the master branch from breaking, this type of work should generally... ork branches. * **Productization** is when the master branch is merged into the stable branch, and the stable branch is then cleaned up to be suitable for use by ever... known bugs. ===== Branches ===== The primary branch is called **master**. All builds are made from it automatically on a... system]]. This means that all development in the master branch must be atomic enough so that the branch remains releasable at any given moment. Other bra

automated_build_system @devel

11 Hits, Last modified: 7 years ago

Every day at 01:00 UTC, the system checks if the master branch has new commits, and if so, tags and builds a new... SourceForge's file distribution servers. ===== Master branch ===== The automated build system operates on the branch called **master**, which is Doomsday's primary development branch. It is crucial that any changes made in the master branch will not break the automated releases. The RSS fe

1.9.8 @version

2 Hits, Last modified: 8 years ago

/mouse input, and low-level networking (including master server comms). Addresses bugs: {{sfbug|2158271}} ... _plugins]] * [[adapt_changes_from_the_mapcache_branch]] * [[double-precision_coordinates]]: BSP buil

developer_guidelines @devel

9 Hits, Last modified: 8 years ago

wish to avoid cross-contaminating code. A feature branch is a branch from the working master that contains a set of changes specific to one ta... en a pull request specifically with that feature branch's changes. ==== Integrate often ==== In order... , try to pull from your base often (e.g. ''origin master''). If you must make a merge commit (without conf... ped in to a commit to the likes of ''Merge origin/master into ...'' or if a more descriptive commit is nee

doomsday-host @multiplayer

3 Hits, Last modified: 8 years ago

ns to use with all server instances. <code xml> <branch>master</branch> <buildDir>/home/jaakko/src/deng/doomsday-build</buildDir> <qmakeCommand>qmake -r ../doomsday/d

getting_started_1.15_or_earlier @devel

18 Hits, Last modified: 9 years ago

nfiguration settings, type: git config -l Your master branch should be tracking //origin//'s (= the GitHub repository) master branch: branch.master.remote=origin branch.master.merge=refs/heads/master remote.origin.url=https://github.com/skyjake/Doomsday-Engine.git remote.origin... in/* You may find it convenient to set a default branch for pulling changes: git config pull.default tr