[[!meta title="Mastering the DragonFly git repository"]]
[[!toc levels=2]]
-## Clone the repository
-
-
-First you go in your work directory and clone the DragonFly repository. While ***crater*** is the official repo, you are urged to use one of our (generally much faster) mirrors instead.
-
- > git clone -o chlamydia git://chlamydia.fs.ei.tum.de/dragonfly.git
-
-If you are a committer, you should create a ***remote*** entry for pushing to ***crater***:
-
- > git remote add crater ssh://crater.dragonflybsd.org/repository/git/dragonfly.git
-
-Clone creates remote-tracking branches for all branches in the parent repo and creates a local **master** branch from the remote **master** branch.
-
- > git branch -a
+## Clone the repository
-
- * master
- chlamydia/DragonFly_RELEASE_1_10
- chlamydia/DragonFly_RELEASE_1_12
- chlamydia/DragonFly_RELEASE_1_2
- chlamydia/DragonFly_RELEASE_1_4
- chlamydia/DragonFly_RELEASE_1_6
- chlamydia/DragonFly_RELEASE_1_8
- chlamydia/DragonFly_RELEASE_2_0
- chlamydia/HEAD
- chlamydia/master
- chlamydia/repo/hooks
- chlamydia/vendor/ATHEROS
- [...]
- chlamydia/vendor/ZLIB
+Look at the [[download]] page on how to clone the DragonFly repository. ***Note***: Please use a git mirror to reduce the bandwidth on the main servers.
## Prepare patches
-If you (as a non-developer) made some changes to the DragonFly source and want to get them included in the main repository, send your patches to submit@lists.dragonflybsd.org. git assists you in creating patches which are easy to handle for the developers.
+If you (as a non-developer) made some changes to the DragonFly source and want to get them included in the main repository, send your patches to `submit@lists.dragonflybsd.org`.
+In order to be able to do that, you need to have yourself and the email address you are using registered with the <http://bugs.dragonflybsd.org/> bug/issue tracker; otherwise, your contribution will get silently dropped.
+Git assists you in creating patches which are easy to handle for the developers.
### Example
**Note:** The change in this example is completely useless, it only serves demonstration purposes!
- > git format-patch origin
+ > git format-patch origin/master
0001-Change-parentheses.patch
> cat 0001-Change-parentheses.patch
From cbb871b4588c695f000bc701b4f3c16a0a518991 Mon Sep 17 00:00:00 2001