From aa3768790954b1ab81dec25b8000963a95ac1d90 Mon Sep 17 00:00:00 2001 From: George Melikov Date: Sat, 1 Apr 2017 19:07:41 +0400 Subject: [PATCH] Updated OpenZFS Patches (markdown) --- OpenZFS-Patches.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OpenZFS-Patches.md b/OpenZFS-Patches.md index 3eed450..c3f48fc 100644 --- a/OpenZFS-Patches.md +++ b/OpenZFS-Patches.md @@ -36,7 +36,7 @@ $ sh autogen.sh && ./configure --enable-debug && make -s -j$(nproc) ### Porting a Patch -**Pick a patch.** Consult the [[OpenZFS tracking]] page and select a patch which has not yet been applied. For your first patch you will want to select a small patch to familiarize yourself with the process. +**Pick a patch.** Consult the [OpenZFS tracking](http://build.zfsonlinux.org/openzfs-tracking.html) page and select a patch which has not yet been applied. For your first patch you will want to select a small patch to familiarize yourself with the process. **Create a new branch.** It is important to create a new branch for every commit you port to ZFS on Linux. This will allow you to easily submit your work as a GitHub pull request and it makes it possible to work on multiple OpenZFS changes concurrently. All development branches need to be based off of the ZFS master branch and it's helpful to name the branches after the issue number you're working on.