Re: [notmuch] nested tag trees (was: Mail in git)

2010-02-18 Thread martin f krafft
also sprach Ben Gamari [2010.02.18.1810 +1300]: > Yeah, this is a bit of a bummer. This is really a stretch, but I wonder > if the git folks would accept patches/minor database semantics changes > in the name of making git more flexible as a general purpose object > database. I really doubt it, bu

[notmuch] nested tag trees (was: Mail in git)

2010-02-18 Thread martin f krafft
ment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature (see http://martin-krafft.net/gpg/) URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100218/5e2c1006/attachment.pgp>

[notmuch] nested tag trees (was: Mail in git)

2010-02-18 Thread martin f krafft
re (see http://martin-krafft.net/gpg/) URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100218/bb928ed1/attachment.pgp>

[notmuch] nested tag trees (was: Mail in git)

2010-02-18 Thread martin f krafft
notmuchmail.org/pipermail/notmuch/attachments/20100218/f74dc6f1/attachment.pgp>

[notmuch] [PATCH] Look for text/html content types ignoring case

2010-02-18 Thread James Westby
On Tue, 16 Feb 2010 19:11:24 +, David Edmondson wrote: > On Tue, 16 Feb 2010 18:51:00 +, James Westby jameswestby.net> wrote: > > Some people send html parts as text/HTML or similar, so do a > > case-sensitive comparison when checking for html parts. > > There are various other places wh

[notmuch] nested tag trees (was: Mail in git)

2010-02-18 Thread martin f krafft
-- oscar wilde spamtraps: madduck.bogus at madduck.net -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature (see http://martin-krafft.net/gpg/) URL: <http://notmuchmai

Re: [notmuch] Git ancestry and sync problems (was: Mail in git)

2010-02-18 Thread martin f krafft
also sprach ra...@free.fr [2010.02.18.2134 +1300]: > I don't understand the problem. Why not just letting all "inbox" > mails in a regular Maildir, and use git only when they have been > explicit archived? I don't archive my mail. I would like to be able to bring mails from the past back into cir

[notmuch] Git ancestry and sync problems (was: Mail in git)

2010-02-18 Thread martin f krafft
u think, and they are out to get you. spamtraps: madduck.bogus at madduck.net -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature (see http://martin-krafft.net/gpg/) URL: <http://notmu

[notmuch] Mail in git

2010-02-18 Thread martin f krafft
scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature (see http://martin-krafft.net/gpg/) URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100218/515dec5b/attachment.pgp>

[notmuch] Mail in git

2010-02-18 Thread martin f krafft
chment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature (see http://martin-krafft.net/gpg/) URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100218/9969da7e/attachment.pgp>

[notmuch] Mail in git

2010-02-18 Thread martin f krafft
pplication/pgp-signature Size: 198 bytes Desc: Digital signature (see http://martin-krafft.net/gpg/) URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100218/a4df7391/attachment.pgp>

[notmuch] [PATCH 2/2] notmuch.el: Replace inline function calls for body cleaning with a hook mechanism.

2010-02-18 Thread David Edmondson
This, and any other patches that I'm using, are now in a repository at git://gitorious.org/notmuch/notmuch.git dme. -- David Edmondson, http://dme.org

[notmuch] Mail in git

2010-02-18 Thread Stewart Smith
On Wed, 17 Feb 2010 14:21:01 +1300, martin f krafft wrote: > What I am wondering is if (explicit) tags couldn't be represented as > tree-objects with this. > > evenless-link ? link a message object with a tree object > evenless?unlink ? unlink a message object from tree object > [repla

[notmuch] [PATCH 2/2] notmuch.el: Replace inline function calls for body cleaning with a hook mechanism.

2010-02-18 Thread David Edmondson
-cl.patch Type: text/x-diff Size: 11289 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100218/838974e6/attachment.patch> -- next part -- dme. -- David Edmondson, http://dme.org

[notmuch] Git ancestry and sync problems (was: Mail in git)

2010-02-18 Thread ra...@free.fr
- "martin f krafft" a ?crit : > Except I fear that as soon as we allow manipulation of the local > store, we'll potentially run into this problem: > > http://notmuchmail.org/pipermail/notmuch/2010/001114.html > id:20100112045152.GA15275 at lapse.rw.madduck.net I don't understand the pr

Re: [notmuch] [PATCH] Look for text/html content types ignoring case

2010-02-18 Thread James Westby
On Tue, 16 Feb 2010 19:11:24 +, David Edmondson wrote: > On Tue, 16 Feb 2010 18:51:00 +, James Westby > wrote: > > Some people send html parts as text/HTML or similar, so do a > > case-sensitive comparison when checking for html parts. > > There are various other places where `equal' is

[notmuch] Git ancestry and sync problems (was: Mail in git)

2010-02-18 Thread Ben Gamari
Excerpts from racin's message of Thu Feb 18 03:34:28 -0500 2010: > > - "martin f krafft" a ?crit : > > > Except I fear that as soon as we allow manipulation of the local > > store, we'll potentially run into this problem: > > > > http://notmuchmail.org/pipermail/notmuch/2010/001114.html >

[notmuch] Git ancestry and sync problems (was: Mail in git)

2010-02-18 Thread Jameson Rollins
ed any deletion phase, using git sounds much more sensible. jamie. -- 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/20100218/4937e011/attachment.pgp>

Re: [notmuch] Git ancestry and sync problems (was: Mail in git)

2010-02-18 Thread Ben Gamari
Excerpts from racin's message of Thu Feb 18 03:34:28 -0500 2010: > > - "martin f krafft" a écrit : > > > Except I fear that as soon as we allow manipulation of the local > > store, we'll potentially run into this problem: > > > > http://notmuchmail.org/pipermail/notmuch/2010/001114.html >

Re: [notmuch] Git ancestry and sync problems (was: Mail in git)

2010-02-18 Thread Jameson Rollins
On Thu, 18 Feb 2010 09:34:28 +0100 (CET), ra...@free.fr wrote: > I don't understand the problem. Why not just letting all "inbox" mails in a > regular Maildir, > and use git only when they have been explicit archived? This way, mails are > added to git only if we want > to save them, and we rare

Re: [notmuch] [PATCH 2/2] notmuch.el: Replace inline function calls for body cleaning with a hook mechanism.

2010-02-18 Thread David Edmondson
This, and any other patches that I'm using, are now in a repository at git://gitorious.org/notmuch/notmuch.git dme. -- David Edmondson, http://dme.org ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch

Re: [notmuch] [PATCH 2/2] notmuch.el: Replace inline function calls for body cleaning with a hook mechanism.

2010-02-18 Thread David Edmondson
On Wed, 17 Feb 2010 14:04:12 +, David Edmondson wrote: > In-lining every possible body cleaning function is difficult to > maintain and doesn't allow users any flexibility. Rather, use a hook > mechanism so that users can choose what cleaning takes place. Improved version attached, including

Re: [notmuch] Git ancestry and sync problems (was: Mail in git)

2010-02-18 Thread racin
- "martin f krafft" a écrit : > Except I fear that as soon as we allow manipulation of the local > store, we'll potentially run into this problem: > > http://notmuchmail.org/pipermail/notmuch/2010/001114.html > id:20100112045152.ga15...@lapse.rw.madduck.net I don't understand the probl

[notmuch] nested tag trees (was: Mail in git)

2010-02-18 Thread Ben Gamari
Excerpts from martin f krafft's message of Wed Feb 17 23:59:43 -0500 2010: > also sprach Ben Gamari [2010.02.18.1744 +1300]: > > I believe you would. The problem isn't the messages (well, that's > > a problem too), it's the fact that the tree (e.g. tab) objects > > which reference the messages are