MIME-Version: 1.0
Sender: awg@xvx.ca
In-Reply-To: <87y5x27z6f.fsf@hermes.hocat.ca>
References: <87y5x27z6f.fsf@hermes.hocat.ca>
Date: Tue, 4 Oct 2011 09:28:20 -0600
Message-ID:
 <CAMoJFUt0xfne=5um5sjKR8Wx8RtRdqPW3zz94hk7goPm3M_8Ow@mail.gmail.com>
Subject: Re: notmuch and git
From: Adam Wolfe Gordon <awg+notmuch@xvx.ca>
To: Tom Prince <tom.prince@ualberta.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: notmuch@notmuchmail.org
Precedence: list

On Mon, Oct 3, 2011 at 11:38, Tom Prince <tom.prince@ualberta.net> wrote:
> I know that having an exclude option for notmuch has been discussed a
> number of times. I have wanted such a feature to be able to ignore the
> .git directroy, since I keep my mail in a git repository. I recently
> discovered a workaround.
>
> If you make .git a text file containing
> ===== .git ====
> gitdir: .notmuch/git
> ===============
> and move the .git directory to .notmuch/git, git will behave as if it is
> a normal repository, and notmuch will ignore .notmuch/git. notmuch will
> warn once about .git not being a mail file, but since it is static, it
> won't warn about it every time one does 'notmuch new'.

I use another workaround, which doesn't require anything in the
notmuch directory:

I initialized a bare repository in /home/adam/.mailgit by running git
init --bare.  Then in my scripts I do:

export GIT_WORK_TREE=/home/adam/mail
cd /home/adam/.mailgit
git ... (any git commands you want)

Git uses the directory specified by GIT_WORK_TREE as the working tree
(where the actual files are), and the current directory as a bare
repository containing just the git metadata.

Because there's nothing git-related in /home/adam/mail, notmuch is
completely unaware of git.

-- 
Adam Wolfe Gordon