summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/valgrind.mdwn
AgeCommit message (Collapse)Author
2019-01-14Note the existing workSamuel Thibault
2019-01-14Note that it's a difficult taskSamuel Thibault
2014-02-26Merge commit 'c954f1095918874c73511ffc13f95eef518a8043'Thomas Schwinge
Conflicts: community/meetings.mdwn
2014-01-06mention that valgrind is in CSamuel Thibault
2013-09-26Missing 2013 copyright year updates.Thomas Schwinge
2013-08-25mention rpctrace, as Justus Winter suggestedSamuel Thibault
2011-03-26Typo fix.Thomas Schwinge
2011-03-26Merge commit '0729272db4fe4563fee46488236d75e9c4700eee'Thomas Schwinge
Conflicts: community/gsoc/project_ideas/libdiskfs_locking.mdwn
2011-03-26Re-integrate GSoC pages with the non-GSoC world.Thomas Schwinge
Remove duplicates, apart from procfs, which should rather be removed from the GSoC items.
2011-03-25gsoc/ideas: Add back () to function namesantrik
IMHO it's clearer that way -- especially in browsers that don't display all text attributes, i.e. all text mode browsers.
2011-03-25gsoc/project_ideas: Restore all project ideas hereantrik
While there is certainly some overlap with other areas, it is *not* acceptable to drop mentors and exercises from GSoC tasks, nor to add random crap, nor do any other changes that make them less useful as GSoC tasks -- and this is *not* obvious if they do not live in the project_ideas namespace. It's also confusing in general. I tried to preserve all valid changes to the task descriptions themself -- though I might have messed up some things. I did leave the now redundant entries in open_tasks in place. Not sure how to deal with them. As the content is virtually identical anyways, they probably should be just turned into stubs pointing here. Or don't list them explicitely at all -- we point out in other places that GSoC ideas are useful in other contexts too... For the future, please refrain from reorganising things here without prior discussion.