Matthew Flatt 19f8f30f63 copy responsible info to "info.rkt" files ... It seems more ideal that `pkg-authors` would be specific enough responsibility, but our existing allocations of responsibility are more fine-grained, and we keep them for now.		2014-01-01 07:27:15 -07:00
..
alpha.rkt	move some test & doc collections out of "racket-" pkgs to new pkgs	2013-10-15 17:50:32 -06:00
batch.rkt	move "props" test configs to test submodules or "info.rkt" files	2013-12-30 12:15:18 -07:00
gc-toplevels.rkt	move some test & doc collections out of "racket-" pkgs to new pkgs	2013-10-15 17:50:32 -06:00
info.rkt	copy responsible info to "info.rkt" files	2014-01-01 07:27:15 -07:00
main.rkt	move some test & doc collections out of "racket-" pkgs to new pkgs	2013-10-15 17:50:32 -06:00
merge.rkt	move some test & doc collections out of "racket-" pkgs to new pkgs	2013-10-15 17:50:32 -06:00
module.rkt	move some test & doc collections out of "racket-" pkgs to new pkgs	2013-10-15 17:50:32 -06:00
mpi.rkt	move some test & doc collections out of "racket-" pkgs to new pkgs	2013-10-15 17:50:32 -06:00
nodep.rkt	move some test & doc collections out of "racket-" pkgs to new pkgs	2013-10-15 17:50:32 -06:00
replace-modidx.rkt	move some test & doc collections out of "racket-" pkgs to new pkgs	2013-10-15 17:50:32 -06:00
update-toplevels.rkt	move some test & doc collections out of "racket-" pkgs to new pkgs	2013-10-15 17:50:32 -06:00
util.rkt	move some test & doc collections out of "racket-" pkgs to new pkgs	2013-10-15 17:50:32 -06:00