Brian Tiger Chow 3eafb3e5ab style(repo): repo.Interface -> repo.Repo ... The pkg.Interface style is modeled after heap.Interface. Generally, I find it helpful for interfaces that have many implementations. It provides clear distinction between the generic interface and the |n| implementations that implement it (which may be interface types themselves). For clients who cannot keep the repo name, one can imagine that the most likely rename is `ipfsrepo`. In that case, `ipfsrepo.Interface` remains meaningful. This is low-pri so it doesn't matter than much. But for the record, the repo.Interface feels appropriate in this use-case.		2015-01-13 03:09:33 -08:00
..
commands	style(repo): repo.Interface -> repo.Repo	2015-01-13 03:09:33 -08:00
daemon	transitioned ipfs2 -> ipfs	2014-11-18 06:15:00 -08:00
io	feat(core): expose IpfsNode.Resolve	2015-01-11 01:23:27 -08:00
.gitignore	ignore testdb	2014-07-05 15:04:04 -07:00
bootstrap_test.go	introducing p2p pkg	2015-01-02 08:46:45 -08:00
bootstrap.go	refactor(repo/config) move config under repo	2015-01-13 03:09:30 -08:00
core_test.go	it's unclear what this test case is meant to protect, but passing an empty datastore value no longer has bearing on node construction. Datastore setup now occurs in repo.	2015-01-13 03:09:31 -08:00
core.go	refactor(repo/config) move config under repo	2015-01-13 03:09:30 -08:00
datastore.go	refactor(repo/config) move config under repo	2015-01-13 03:09:30 -08:00
mock.go	core/mock: use mock routing	2015-01-05 00:16:53 -08:00