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

[martin f krafft]

also sprach racin at 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 circulation at any time, without duplicating
them, or potentially having to discard the metadata when moving them
into a Maildir.

-- 
martin | http://madduck.net/ | http://two.sentenc.es/

"aus der kriegsschule des lebens -
 was mich nicht umbringt, macht mich h?rter."
 - friedrich nietzsche

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: 

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

[martin f krafft]

also sprach martin f krafft  [2010.02.18.1500 +1300]:
> > > If we keep ancestry though, we are reusing existing working code for
> > > backup (git-pull :)
> > 
> > This is one of the reasons I feel it's important we keep it. And as is
> > stated below, the storage overhead is minimal.
> 
> Absolutely; Stewart mentioned at LCA to forego the porcelain and
> harness the power of the plumbing, and I knew back then that this
> would be among the first things of which to convince him once he had
> the basic idea out. ;)

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

-- 
martin | http://madduck.net/ | http://two.sentenc.es/

it's as bad as you 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: 

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

[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 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 rarely (never?) need to remove mail from the git store. 
Deleting mail
is also much easier to do from the maildir. This mail flow would make much more 
sense to me.

Thanks,
Matthieu

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

[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
> >   id:20100112045152.GA15275 at lapse.rw.madduck.net
> 
> 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 rarely (never?) need to remove mail from the git store. 
> Deleting mail
> is also much easier to do from the maildir. This mail flow would make much 
> more sense to me.

Yes, this would certainly be much easier, but by doing this you also
pass up on using much of git's utility (although as we've discovered,
using it is non-trivial). In particular, I am very interested in using
git to keep my mail and tags synchronized across multiple machines. This
is an issue that I've always struggled with: While I dislike having my
mail tied to my laptop, there is no good two-way solution for
synchronizing maildirs and metadata across machines.

- Ben

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

[Jameson Rollins]

On Thu, 18 Feb 2010 09:34:28 +0100 (CET), racin at 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 rarely (never?) need to remove mail from the git store. 
> Deleting mail
> is also much easier to do from the maildir. This mail flow would make much 
> more sense to me.

I agree that this sounds much simpler and far easier to implement.  Once
you're passed 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: 

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

[racin]

- martin f krafft madd...@madduck.net 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 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 rarely (never?) need to remove mail from the git store. 
Deleting mail
is also much easier to do from the maildir. This mail flow would make much more 
sense to me.

Thanks,
Matthieu

___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

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

[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 rarely (never?) need to remove mail from the git store. 
 Deleting mail
 is also much easier to do from the maildir. This mail flow would make much 
 more sense to me.

I agree that this sounds much simpler and far easier to implement.  Once
you're passed any deletion phase, using git sounds much more sensible.

jamie.


pgpkD9FbTF7PP.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

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

[martin f krafft]

also sprach ra...@free.fr 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 circulation at any time, without duplicating
them, or potentially having to discard the metadata when moving them
into a Maildir.

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
aus der kriegsschule des lebens -
 was mich nicht umbringt, macht mich härter.
 - friedrich nietzsche
 
spamtraps: madduck.bo...@madduck.net


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch