This change is in anticipation of moving pkg/images to go4.org, where it
should not depend on packages in third_party.
So:
third_party/github.com/nf/cr2 -> vendor/github.com/nf/cr2
third_party/github.com/rwcarlsen/goexif -> vendor/github.com/rwcarlsen/goexif
third_party/golang.org/x/image/tiff -> vendor/golang.org/x/image/tiff
Note that third_party/go/pkg/image/jpeg was also a dependency of
pkg/images. We had vendored image/jpeg from tip at the time because it
offered advantages over the version from Go1.3
(https://github.com/camlistore/camlistore/issues/463).
Since we now depend on Go1.5, we can go back to depend on the stdlib
version, so we simply remove third_party/go/pkg/image/jpeg and adjust
the imports accordingly.
Change-Id: Ifc8ffae0551102e644a0a0c67f3ff89e04df15c7
oauth2 at 267028f9bc2a1177dc5769be38c68c1b4fbe91c4
google cloud at 2e43671e4ad874a7bca65746ff3edb38e6e93762
google api at fc402b0d6f2a46ba7dcf0a4606031f45fb82a728
(partial commit only, since it's 16+ MB)
And update all callers from the old
code.google.com/p/google-api-go-client over to google.golang.org/api.
Change-Id: Ide190e04bb863928f98369a7c4d2b8c19fda1f66
I think these snuck in because not everyone has the client side git
hooks registered to check on misc/review.
Removed third_party/github.com/bradfitz/latlong/gen_test.go (per
review feedback)
Change-Id: Ide09d152b28157a043009d7285f1afd4a60ac9de
generate.go cannot be used without the datafiles, which we
have not imported.
also rewrote some commented out imports.
Change-Id: If97e4604df52b9533fc0412a7ebd8a3be0470233
Creates new page @ /ui/mobile.html for generating a QR code that
embeds configuration data for setting up mobile clients.
Imports code.google.com/p/rsc/{gf256,qr} version:
parent: 149:a3cbaf2339c4 tip
This addresses the server and web components of
https://camlistore.org/issue/372
Change-Id: If9239dd138707080afd7dedb5770d04893cbf0ba
import bazil.org/fuse at f6649cd46fb76b1e04ba9eeffb773cb189278d31
remove code.google.com/p/rsc/fuse.
Huge thanks to Tommi Virtanen for the fuse support.
Change-Id: I44b95ac1ea344648593c7376f83ca675a56077b3
of enumerating Drive files, needs to be fixed once Drive supports
range queries. Allows you to sync to /sto-googledrive/, but not from.
Change-Id: I6ac5ef02c5f51a6abdab5c207a3a5693c6bb8581
A planned permanode involves setting the contents of the permanode
(instead of a random string) as well as the OpenPGP signing time so
the resultant bytes of the blob (and thus its blobref) is deterministic.
This allows multiple independent devices (my laptops) to create the
same permanodes for the same files (photos backed up from my phone)
when offline (airplane) and then when they sync later, still only have
one permanode per unique file. This means that tagging and other
metadata applied to permanodes on one laptop merge cleanly with
metadata from the other.
when truncating nodes without the Handle valid bit set, seek out
all open handles for that Node.
requires maintaining mapping info between nodes and handles.
Change-Id: I27955a60dda2ca354d66e87e34b31f3894615c41