diff options
| author | antrik <antrik@users.sf.net> | 2009-03-11 21:43:25 +0100 |
|---|---|---|
| committer | antrik <antrik@users.sf.net> | 2009-03-12 09:16:48 +0100 |
| commit | 2730e7e10d485e23185e755f82662b749d8143df (patch) | |
| tree | d8093a739e161908cf846bc79b767535594ebbb0 /community/gsoc/project_ideas/libdiskfs_locking.mdwn | |
| parent | cd875551b32b895f4049bc94e78067f2cd4783ec (diff) | |
Diskfs locking GSoC task: Change exercise
The result of the previous exercise probably couldn't be considered a
useful patch -- not suitable for going into mainline at least.
Diffstat (limited to 'community/gsoc/project_ideas/libdiskfs_locking.mdwn')
| -rw-r--r-- | community/gsoc/project_ideas/libdiskfs_locking.mdwn | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/community/gsoc/project_ideas/libdiskfs_locking.mdwn b/community/gsoc/project_ideas/libdiskfs_locking.mdwn index 7212ac8f..03914078 100644 --- a/community/gsoc/project_ideas/libdiskfs_locking.mdwn +++ b/community/gsoc/project_ideas/libdiskfs_locking.mdwn @@ -32,4 +32,7 @@ applications. Possible mentors: ? -Exercise: Hack libdiskfs to keep count of the number of locks currently held. +Exercise: If you could actually track down and fix one of the existing locking +errors before the end of the application process, that would be excellent. This +might be rather tough though, so probably you need to talk to us about an +alternative exercise task... |