From: Ben Gamari <bgamari@gmail.com>
To: racin <racin@free.fr>
Cc: martin f krafft <madduck@madduck.net>, notmuch <notmuch@notmuchmail.org>
Subject: Re: Git ancestry and sync problems (was: Mail in git)
Date: Thu, 18 Feb 2010 07:47:35 -0500 [thread overview]
Message-ID: <1266497097-sup-6128@ben-laptop> (raw)
In-Reply-To: <899270357.3379251266482068203.JavaMail.root@zimbra1-e1.priv.proxad.net>
Excerpts from racin's message of Thu Feb 18 03:34:28 -0500 2010:
>
> ----- "martin f krafft" <madduck@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.GA15275@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
next prev parent reply other threads:[~2010-02-18 12:47 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
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 [this message]
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=1266497097-sup-6128@ben-laptop \
--to=bgamari@gmail.com \
--cc=madduck@madduck.net \
--cc=notmuch@notmuchmail.org \
--cc=racin@free.fr \
/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).