From: David Bremner <david@tethera.net>
To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org
Subject: Re: hack to retag a directory
Date: Sat, 06 Feb 2010 19:38:03 -0400 [thread overview]
Message-ID: <87iqaaue90.fsf@rocinante.cs.unb.ca> (raw)
In-Reply-To: <87ock3cf8j.fsf@yoom.home.cworth.org>
On Fri, 05 Feb 2010 17:41:48 -0800, Carl Worth <cworth@cworth.org> wrote:
[talking about gitmuch, a simple wrapper around notmuch dump && git commit]
>
> And it's interesting that this script might be just good enough for the
> synchronization needs of some people. It's not integrated, and might
> require manual fixup of any resulting git conflicts, but it might be
> handy for some.
>
I have to say that merge conflicts are not very much fun. I tend to do a
certain amount of oh, take all the changes from the server. I wonder if
the approach that someone else mentioned of keeping a file
tags/message-id with the appropriate tags in it might make merging less
painful.
> The biggest problem I see is that if I were to read some messages
> locally, and then run "gitmuch restore" then this would wipe out the
> local changes I had made. So we'll definitely want a more integrated
> solution to eliminate the chance of problems like this.
Yeah, the footgun potential is definitely there.
> One easy answer is to just make "notmuch restore" do nothing for
> messages where the existing tags are the same as the tags mentioned in
> the input file. I just pushed a change to implement this, (along with
> new tests for "notmuch dump" and "notmuch restore" of course).
Heh, I think I later posted a patch to do that as well.
d
next prev parent reply other threads:[~2010-02-06 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 13:39 hack to retag a directory david
2009-12-03 19:26 ` david
2010-02-06 1:41 ` Carl Worth
2010-02-06 23:38 ` David Bremner [this message]
2010-02-06 23:59 ` 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=87iqaaue90.fsf@rocinante.cs.unb.ca \
--to=david@tethera.net \
--cc=cworth@cworth.org \
--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).