notmuch-next branch

2010-10-11 Thread Amit Kucheria
On Mon, Oct 11, 2010 at 10:01 PM, Jameson Rollins wrote: > On Mon, 11 Oct 2010 21:45:47 +0300, Felipe Contreras gmail.com> wrote: >> I think many people agree notmuch mainline has been rather slow. So >> I'm proposing to have notmuch-next branch, either on github or >> gitorious (please vote).

sluk, rss and notmuch - some use cases

2010-10-11 Thread Kristoffer Ström
I just wrote a simple script to turn rss feeds into notmuch-parsable directories. Script and docs available at: http://github.com/krl/sluk/ I had run into problems with both of the two other solutions for this i know feed2imap: problems with threading consuming 100% cpu somehow (seems like a

notmuch-next branch

2010-10-11 Thread Jed Brown
On Mon, Oct 11, 2010 at 22:00, Jameson Rollins wrote: > As long as all the repos are synced, then you only need to track one. > But notmuch already has "official" repos [0], and making another > pseudo-"official" repo will probably just makes things more confusing. Patches show up in a different

notmuch-next branch

2010-10-11 Thread Felipe Contreras
Hi, I think many people agree notmuch mainline has been rather slow. So I'm proposing to have notmuch-next branch, either on github or gitorious (please vote). More than one person should have write access to this repo, but some guidelines should be in place. I propose that patches should be

notmuch-next branch

2010-10-11 Thread Kristoffer Ström
> What do you think? Good idea. github+

notmuch-next branch

2010-10-11 Thread Jesse Rosenthal
On Mon, 11 Oct 2010 22:10:24 +0200, Jed Brown wrote: > Patches show up in a different order in each person's "personal, but > 'synced'" repository. Then you need a mess of merges to actually get > them synced (if they are published, you can't rebase). I'd add, by way of voting for something a

notmuch-next branch

2010-10-11 Thread Jameson Rollins
tachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20101011/59d54bab/attachment.pgp>

notmuch-next branch

2010-10-11 Thread Jameson Rollins
-- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20101011/b1e06538/attachment.pgp>

notmuch-next branch

2010-10-11 Thread Servilio Afre Puentes
On 11 October 2010 14:45, Felipe Contreras wrote: > Hi, > > I think many people agree notmuch mainline has been rather slow. So > I'm proposing to have notmuch-next branch, either on github or > gitorious (please vote). +1 for gitorious, you can use OpenID and their code is available (for me a

[PATCH 3/3] notmuch-tag.c: Add tag logging.

2010-10-11 Thread da...@tethera.net
From: David Bremner logging of tags is enabled by adding a stanza like [log] tags = /some/path/you/can/write/to to your notmuch config. Note that we intentionally do the logging after the database transaction is finished. --- notmuch-tag.c | 31

[PATCH 2/3] notmuch-log.c: Add a function to log a pair of strings with a timestamp.

2010-10-11 Thread da...@tethera.net
From: David Bremner Since the function is supposed to work for any pair of strings, this means some form of quoting seems necessary. I decided to re-use the json quoting routines for convenience. --- notmuch-client.h |4 notmuch-log.c| 18 ++ 2

[PATCH 1/3] Initial implementation of low level logging routines.

2010-10-11 Thread da...@tethera.net
From: David Bremner notmuch_log_open: open a log file; just a wrapper around open(2) notmuch_log_append: atomically append a buffer (character array) to a log file Based on per-write file locking, performance will have to be tested. --- Makefile.local |1 +

First draft of logging functionality.

2010-10-11 Thread da...@tethera.net
The patches following this message are my first attempt at implementing atomic logging for notmuch. The idea is that such logs could be useful in synchronizing notmuch instances. Feedback of any kind is welcome. I'm particularly interested in comments about the log format and performance. In my

First draft of logging functionality.

2010-10-11 Thread david
The patches following this message are my first attempt at implementing atomic logging for notmuch. The idea is that such logs could be useful in synchronizing notmuch instances. Feedback of any kind is welcome. I'm particularly interested in comments about the log format and performance. In my

[PATCH 1/3] Initial implementation of low level logging routines.

2010-10-11 Thread david
From: David Bremner brem...@unb.ca notmuch_log_open: open a log file; just a wrapper around open(2) notmuch_log_append: atomically append a buffer (character array) to a log file Based on per-write file locking, performance will have to be tested. --- Makefile.local |1 + notmuch-client.h

[PATCH 2/3] notmuch-log.c: Add a function to log a pair of strings with a timestamp.

2010-10-11 Thread david
From: David Bremner brem...@unb.ca Since the function is supposed to work for any pair of strings, this means some form of quoting seems necessary. I decided to re-use the json quoting routines for convenience. --- notmuch-client.h |4 notmuch-log.c| 18 ++ 2 files

notmuch-next branch

2010-10-11 Thread Felipe Contreras
Hi, I think many people agree notmuch mainline has been rather slow. So I'm proposing to have notmuch-next branch, either on github or gitorious (please vote). More than one person should have write access to this repo, but some guidelines should be in place. I propose that patches should be

Re: notmuch-next branch

2010-10-11 Thread Servilio Afre Puentes
On 11 October 2010 14:45, Felipe Contreras felipe.contre...@gmail.com wrote: Hi, I think many people agree notmuch mainline has been rather slow. So I'm proposing to have notmuch-next branch, either on github or gitorious (please vote). +1 for gitorious, you can use OpenID and their code is

Re: notmuch-next branch

2010-10-11 Thread Jameson Rollins
On Mon, 11 Oct 2010 21:45:47 +0300, Felipe Contreras felipe.contre...@gmail.com wrote: I think many people agree notmuch mainline has been rather slow. So I'm proposing to have notmuch-next branch, either on github or gitorious (please vote). More than one person should have write access to

Re: notmuch-next branch

2010-10-11 Thread Servilio Afre Puentes
On 11 October 2010 15:01, Jameson Rollins jroll...@finestructure.net wrote: On Mon, 11 Oct 2010 21:45:47 +0300, Felipe Contreras felipe.contre...@gmail.com wrote: I think many people agree notmuch mainline has been rather slow. So I'm proposing to have notmuch-next branch, either on github or

Re: notmuch-next branch

2010-10-11 Thread Jed Brown
On Mon, Oct 11, 2010 at 22:00, Jameson Rollins jroll...@finestructure.net wrote: As long as all the repos are synced, then you only need to track one. But notmuch already has official repos [0], and making another pseudo-official repo will probably just makes things more confusing. Patches

sluk, rss and notmuch - some use cases

2010-10-11 Thread Kristoffer Ström
I just wrote a simple script to turn rss feeds into notmuch-parsable directories. Script and docs available at: http://github.com/krl/sluk/ I had run into problems with both of the two other solutions for this i know feed2imap: problems with threading consuming 100% cpu somehow (seems like a

Re: notmuch-next branch

2010-10-11 Thread Felipe Contreras
On Mon, Oct 11, 2010 at 10:01 PM, Jameson Rollins jroll...@finestructure.net wrote: On Mon, 11 Oct 2010 21:45:47 +0300, Felipe Contreras felipe.contre...@gmail.com wrote: I think many people agree notmuch mainline has been rather slow. So I'm proposing to have notmuch-next branch, either on