From: Michal Sojka <sojkam1@fel.cvut.cz>
To: david@tethera.net, notmuch@notmuchmail.org
Subject: Re: First draft of logging functionality.
Date: Tue, 12 Oct 2010 11:06:17 +0200 [thread overview]
Message-ID: <87zkuj3hme.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <1286803617-17328-1-git-send-email-david@tethera.net>
On Mon, 11 Oct 2010, david@tethera.net wrote:
> 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.
Hi David,
I'm not sure whether implementing logging facility outside of notmuch
library is a good thing. If somebody will use a third-party tool (such
as python bindings) to manipulate his tags, they won't appear in the
log.
-Michal
next prev parent reply other threads:[~2010-10-12 9:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 13:26 First draft of logging functionality david
2010-10-11 13:26 ` [PATCH 1/3] Initial implementation of low level logging routines david
2010-10-11 13:26 ` [PATCH 2/3] notmuch-log.c: Add a function to log a pair of strings with a timestamp david
2010-10-11 13:26 ` [PATCH 3/3] notmuch-tag.c: Add tag logging david
2010-10-12 9:06 ` Michal Sojka [this message]
2010-10-12 11:21 ` First draft of logging functionality David Bremner
2010-10-12 11:38 ` Michal Sojka
2010-10-12 13:16 ` David Bremner
2010-10-12 14:32 ` Rob Browning
2010-10-24 21:01 ` Second draft of logging patches david
2010-11-10 3:18 ` David Bremner
2010-11-13 5:25 ` Michal Sojka
2010-11-13 12:11 ` David Bremner
2010-10-24 21:01 ` [PATCH 1/4] Initial implementation of low level logging routines david
2010-10-24 21:01 ` [PATCH 2/4] Add log component to database struct david
2010-10-24 21:01 ` [PATCH 3/4] Add logging to low level message handling routines david
2010-10-24 21:01 ` [PATCH 4/4] Enable logging in notmuch-tag.c david
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zkuj3hme.fsf@steelpick.2x.cz \
--to=sojkam1@fel.cvut.cz \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).