Processed: Re: Bug#863863: ITP: gmailieer -- Fast fetch and two-way tag synchronization between notmuch and GMail
Processing control commands: > tag -1 pending Bug #863863 [wnpp] ITP: gmailieer -- Fast fetch and two-way tag synchronization between notmuch and GMail Added tag(s) pending. -- 863863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#863863: ITP: gmailieer -- Fast fetch and two-way tag synchronization between notmuch and GMail
Control: tag -1 pending On Thu, Jun 01, 2017 at 09:13:09AM +0200, Julian Andres Klode wrote: > Package: wnpp > Severity: wishlist > Owner: Julian Andres Klode> > (gauteh: this is a Debian packaging intent) > > * Package name: gmailieer > Version : 0.1+git > Upstream Author : Gaute Hope > * URL : https://github.com/gauteh/gmailieer > * License : GPL-3+ > Programming Lang: Python > Description : Fast fetch and two-way tag synchronization between > notmuch and GMail > > This program can pull email and labels (and changes to labels) from your > GMail account > and store them locally in a maildir with the labels synchronized with a > notmuch database. > The changes to tags in the notmuch database may be pushed back remotely to > your GMail account. > > It will not and can not: > > - Add or delete messages on your remote account > - Modify messages other than their labels Uploaded to NEW. Packaging in Salsa. Sorry it took so long :( -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#863863: ITP: gmailieer -- Fast fetch and two-way tag synchronization between notmuch and GMail
On Thu, Jun 01, 2017 at 09:13:09AM +0200, Julian Andres Klode wrote: > Package: wnpp > Severity: wishlist > Owner: Julian Andres Klode> > (gauteh: this is a Debian packaging intent) > > * Package name: gmailieer > Version : 0.1+git > Upstream Author : Gaute Hope > * URL : https://github.com/gauteh/gmailieer > * License : GPL-3+ > Programming Lang: Python > Description : Fast fetch and two-way tag synchronization between > notmuch and GMail > > This program can pull email and labels (and changes to labels) from your > GMail account > and store them locally in a maildir with the labels synchronized with a > notmuch database. > The changes to tags in the notmuch database may be pushed back remotely to > your GMail account. > > It will not and can not: > > - Add or delete messages on your remote account > - Modify messages other than their labels > > PS. I'm not subscribed to -devel, so please do not only reply > there. (I can respond via nntp, but I don't really look at it). > Early packaging in https://anonscm.debian.org/git/collab-maint/gmailieer.git (cgit might not be live yet). -- Debian Developer - deb.li/jak | jak-linux.org - free software dev | Ubuntu Core Developer | When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to ('inline'). Thank you.
Bug#863863: ITP: gmailieer -- Fast fetch and two-way tag synchronization between notmuch and GMail
Package: wnpp Severity: wishlist Owner: Julian Andres Klode(gauteh: this is a Debian packaging intent) * Package name: gmailieer Version : 0.1+git Upstream Author : Gaute Hope * URL : https://github.com/gauteh/gmailieer * License : GPL-3+ Programming Lang: Python Description : Fast fetch and two-way tag synchronization between notmuch and GMail This program can pull email and labels (and changes to labels) from your GMail account and store them locally in a maildir with the labels synchronized with a notmuch database. The changes to tags in the notmuch database may be pushed back remotely to your GMail account. It will not and can not: - Add or delete messages on your remote account - Modify messages other than their labels PS. I'm not subscribed to -devel, so please do not only reply there. (I can respond via nntp, but I don't really look at it). -- Debian Developer - deb.li/jak | jak-linux.org - free software dev | Ubuntu Core Developer | When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to ('inline'). Thank you.