aboutsummaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/valgrind.mdwn
Commit message (Collapse)AuthorAgeFilesLines
* Merge commit 'c954f1095918874c73511ffc13f95eef518a8043'Thomas Schwinge2014-02-261-3/+3
|\ | | | | | | | | Conflicts: community/meetings.mdwn
| * mention that valgrind is in CSamuel Thibault2014-01-061-1/+1
|/
* Missing 2013 copyright year updates.Thomas Schwinge2013-09-261-1/+1
|
* mention rpctrace, as Justus Winter suggestedSamuel Thibault2013-08-251-0/+2
|
* Typo fix.Thomas Schwinge2011-03-261-1/+1
|
* Merge commit '0729272db4fe4563fee46488236d75e9c4700eee'Thomas Schwinge2011-03-261-4/+4
|\ | | | | | | | | Conflicts: community/gsoc/project_ideas/libdiskfs_locking.mdwn
| * gsoc/ideas: Add back () to function namesantrik2011-03-251-4/+4
| | | | | | | | | | IMHO it's clearer that way -- especially in browsers that don't display all text attributes, i.e. all text mode browsers.
* | Re-integrate GSoC pages with the non-GSoC world.Thomas Schwinge2011-03-261-0/+2
|/ | | | | Remove duplicates, apart from procfs, which should rather be removed from the GSoC items.
* gsoc/project_ideas: Restore all project ideas hereantrik2011-03-251-0/+81
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.