Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2019-08-22 | Recursive revbump from boost-1.71.0 | ryoon | 1 | -2/+2 | |
2019-07-20 | *: recursive bump for nettle 3.5.1 | wiz | 1 | -2/+2 | |
2019-07-01 | Recursive revbump from boost-1.70.0 | ryoon | 1 | -2/+2 | |
2018-12-13 | revbump for boost 1.69.0 | adam | 1 | -2/+2 | |
2018-08-16 | revbump after boost-libs update | adam | 1 | -2/+2 | |
2018-04-29 | revbump for boost-libs update | adam | 1 | -2/+2 | |
2018-01-01 | Revbump after boost update | adam | 1 | -2/+2 | |
2017-08-24 | Revbump for boost update | adam | 1 | -2/+2 | |
2017-04-30 | Recursive revbump from boost update | ryoon | 1 | -2/+2 | |
2017-01-01 | Revbump after boost update | adam | 1 | -2/+2 | |
2016-10-07 | Revbump post boost update | adam | 1 | -2/+2 | |
2016-07-04 | Drop dependency on libiberty - its not needed, besides which its toxic and ↵ | abs | 1 | -3/+2 | |
breaks any later builds of pkgsrc gcc. Bump PKGREVISION | |||||
2016-03-05 | Bump PKGREVISION for security/openssl ABI bump. | jperkin | 1 | -1/+2 | |
2015-11-09 | Updated net/grive2 to 0.4.1 | abs | 1 | -9/+4 | |
Changelog only has "Bug fixes" Several pkgsrc patches merged pkgsrc changes: Switch to new Github handling | |||||
2015-06-25 | Needs pkg-config. | joerg | 1 | -1/+2 | |
2015-06-16 | Added net/grive2 version 0.4.0.20150531 | abs | 1 | -0/+36 | |
This is the fork of original "Grive" (https://github.com/Grive/grive) Google Drive client with the support for the new Drive REST API and partial sync. Grive can be considered still beta or pre-beta quality. It simply downloads all the files in your Google Drive into the current directory. After you make some changes to the local files, run grive again and it will upload your changes back to your Google Drive. New files created locally or in Google Drive will be uploaded or downloaded respectively. Deleted files will also be "removed". Currently Grive will NOT destroy any of your files: it will only move the files to a directory named .trash or put them in the Google Drive trash. You can always recover them. |