summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas
diff options
context:
space:
mode:
authorhttps://me.yahoo.com/a/g3Ccalpj0NhN566pHbUl6i9QF0QEkrhlfPM-#b1c14 <diana@web>2015-02-16 20:13:00 +0100
committerGNU Hurd web pages engine <web-hurd@gnu.org>2015-02-16 20:13:00 +0100
commitac8a5d3f653f60d4d759b2afbddcf623eee73dc6 (patch)
treefe6419fbefb2648bab1a56a4882a475c2e16da27 /community/gsoc/project_ideas
parent70046517e26ad2143872d8011cfda2df39531fcd (diff)
update for rename of open_issues/security.mdwn to service_solahart_jakarta_selatan__082122541663/security.mdwn
Diffstat (limited to 'community/gsoc/project_ideas')
-rw-r--r--community/gsoc/project_ideas/libdiskfs_locking.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/community/gsoc/project_ideas/libdiskfs_locking.mdwn b/community/gsoc/project_ideas/libdiskfs_locking.mdwn
index ab3ac93d..bfd1561e 100644
--- a/community/gsoc/project_ideas/libdiskfs_locking.mdwn
+++ b/community/gsoc/project_ideas/libdiskfs_locking.mdwn
@@ -26,7 +26,7 @@ runtime. Or implementing a [[service_solahart_jakarta_selatan__082122541663/unit
locking in various code paths. (The latter could serve as a template for
implementing unit tests in other parts of the Hurd codebase...)
-(A [[systematic code review|open_issues/security]] would probably suffice to find the
+(A [[systematic code review|service_solahart_jakarta_selatan__082122541663/security]] would probably suffice to find the
existing locking
issues; but it wouldn't document the work in terms of actual code produced, and
thus it's not suitable for a GSoC project...)