summaryrefslogtreecommitdiff
path: root/community
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2015-02-18 00:57:00 +0100
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2015-02-18 00:57:00 +0100
commit2bd29189af219a8468971ce89b0a7c70c40dcf79 (patch)
treeeca60b292a4935ed1ef8cd2012bcc1596cffca07 /community
parentc5604a1f1b7152fe435a69a0b2b7fd400c45fc15 (diff)
Revert "update for rename of open_issues/security.mdwn to service_solahart_jakarta_selatan__082122541663/security.mdwn"
This reverts commit ac8a5d3f653f60d4d759b2afbddcf623eee73dc6.
Diffstat (limited to 'community')
-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 bfd1561e..ab3ac93d 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|service_solahart_jakarta_selatan__082122541663/security]] would probably suffice to find the
+(A [[systematic code review|open_issues/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...)