WWW-www.enlightenment.org pushed a commit to branch master.
http://git.enlightenment.org/website/www-content.git/commit/?id=5a13ad1d2641d4100852e9a76bef1a0ad763bd6c
commit 5a13ad1d2641d4100852e9a76bef1a0ad763bd6c
Author: Stefan Schmidt <ste...@datenfreihafen.org>
Date: Thu Nov 30 23:49:50 2017 -0800
Wiki page git-guide.md changed with summary [The build your own branch
(BYOB) idea never really worked out] by Stefan Schmidt
---
pages/contrib/devs/git-guide.md.txt | 2 --
1 file changed, 2 deletions(-)
diff --git a/pages/contrib/devs/git-guide.md.txt
b/pages/contrib/devs/git-guide.md.txt
index 98bfaa39d..e5a174ea6 100644
--- a/pages/contrib/devs/git-guide.md.txt
+++ b/pages/contrib/devs/git-guide.md.txt
@@ -123,8 +123,6 @@ Every developer can create their own branches inside a
repository. The naming mu
These branches can be used if you're implementing a larger feature and want to
share your progress with other developers.
-The branch named ``devs/{devname}/jenkins`` has a special meaning: Jenkins
will automatically try to build this branch for you and report any warnings and
errors. The results are available [from the Jenkins BYOB
page](http://jenkins.enlightenment.org/view/BYOB/).
-
#### Creating a Developer Branch ####
Create a developer branch by pushing it to the remote repository:
--
