From: Ben Gamari <bgamari@gmail.com>
To: Mark Anderson <markr.anderson@amd.com>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: Mail in git
Date: Wed, 17 Feb 2010 14:34:31 -0500 [thread overview]
Message-ID: <1266435265-sup-5024@ben-laptop> (raw)
In-Reply-To: <3wd3a0z7jjv.fsf@mhdcelk-nx01.amd.com>
Excerpts from Mark Anderson's message of Wed Feb 17 14:23:48 -0500 2010:
> But if we have notmuch as a cache of the tags, then don't we already
> know the tree objects that need updating? Yes, we would probably need
> some consistency checks for when things don't work as planned, but in
> the common case we ought to always know.
>
Cached or not, rewriting would still be an incredibly (e.g.
prohibitively or close to it) expensive operation for a large mailstore.
> Perhaps I'm misunderstanding these tree objects, and you're suggesting
> that we don't even tell notmuch about them.
>
I think it would be unwise to teach notmuch anything about the
underlying store. That would be leaking way too many implementation
details into
- Ben
next prev parent reply other threads:[~2010-02-17 19:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 0:29 Mail in git Stewart Smith
2010-02-16 9:08 ` Michal Sojka
2010-02-16 19:06 ` Ben Gamari
2010-02-17 0:21 ` Stewart Smith
2010-02-17 10:07 ` Stewart Smith
2011-05-21 7:05 ` martin f krafft
2011-05-21 7:25 ` Stewart Smith
2010-02-17 1:21 ` martin f krafft
2010-02-17 15:03 ` Ben Gamari
2010-02-17 19:23 ` Mark Anderson
2010-02-17 19:34 ` Ben Gamari [this message]
2010-02-17 23:52 ` martin f krafft
2010-02-18 0:39 ` Ben Gamari
2010-02-18 1:58 ` martin f krafft
2010-02-18 2:19 ` Ben Gamari
2010-02-18 2:48 ` nested tag trees (was: Mail in git) martin f krafft
2010-02-18 4:32 ` martin f krafft
[not found] ` <1266463007-sup-8777@ben-laptop>
2010-02-18 4:34 ` martin f krafft
[not found] ` <20100218034613.GD1991@lapse.rw.madduck.net>
2010-02-18 4:44 ` Ben Gamari
2010-02-18 4:59 ` martin f krafft
2010-02-18 5:10 ` Ben Gamari
2010-02-19 0:31 ` martin f krafft
2010-02-19 9:52 ` Michal Sojka
2010-02-19 14:27 ` Ben Gamari
2010-02-17 23:56 ` Mail in git Stewart Smith
2010-02-18 1:01 ` Ben Gamari
2010-02-18 2:00 ` martin f krafft
2010-02-18 2:11 ` Git ancestry and sync problems (was: Mail in git) martin f krafft
2010-02-18 8:34 ` racin
2010-02-18 12:20 ` Jameson Rollins
2010-02-18 12:47 ` Ben Gamari
2010-02-18 23:23 ` martin f krafft
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=1266435265-sup-5024@ben-laptop \
--to=bgamari@gmail.com \
--cc=markr.anderson@amd.com \
--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).