From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup-sync & missing message-ids
Date: Tue, 24 Jul 2007 17:05:23 -0700 [thread overview]
Message-ID: <1185321635-sup-1576@south> (raw)
In-Reply-To: <20070724181358.GA20393@electricrain.com>
Excerpts from Dan Sully's message of Tue Jul 24 11:13:58 -0700 2007:
> I've attached a patch which is working for me with message-id.. a bit
> of a hack.
Thanks. I've committed a modification of this. (I create the message-id by
hashing the raw header text, which hopefully this should have all the nice
uniqueness and consistency properties a message id should have.)
> Any issues with running sup-sync via cron ?
Shouldn't be, though that only works if you haven't used your iphone
between the last cron run and when you invoke sup. Unless the folder is
really large, you might instead consider running sup-sync immediately
before running Sup and considering it an annoying startup delay. :)
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-07-25 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 17:48 Dan Sully
2007-07-24 17:56 ` William Morgan
2007-07-24 18:13 ` Dan Sully
2007-07-25 0:05 ` William Morgan [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1185321635-sup-1576@south \
--to=wmorgan-sup@masanjin.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox