From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup-sync-back not syncing all usual sources
Date: Tue, 10 Jul 2007 11:21:57 -0700 [thread overview]
Message-ID: <1184091559-sup-1633@south> (raw)
In-Reply-To: <1182126871-sup-7739@mona>
Excerpts from jeff.covey's message of Sun Jun 17 18:00:24 -0700 2007:
> thanks, it now spits out the names of all of my usual sources and
> moves deleted files from some, but not all of them.
This I'm still not sure about and I can't replicate. a) Does it still
happen with recent SVN, and b) are there any distinguishing features
about which sources it moves stuff from and which it wrongly ignores?
> would it make more sense for sup-sync-back to process only those
> sources which need to be synced back (at this stage in sup-sync-back's
> life, those which have spam/deleted messages)?
Great idea. This is in SVN now.
> also, at the end of running sup-sync-back without specifying a source, i get
> this:
>
> Scanning sup://sent...
> Scanned 4, deleted 0, moved 0 messages from sup://sent.
> [Sun Jun 17 20:32:34 -0400 2007] saving index and sources...
> [Sun Jun 17 20:32:35 -0400 2007] unlocking /home/jeff/.sup/lock...
> /usr/lib/ruby/1.8/fileutils.rb:505:in `rename': No such file or directory -
> /tmp/sup-sync-back-9998.1089.0 or (Errno::ENOENT)
This should be fixed as well.
Let me know how things are working for you.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-07-10 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 16:13 jeff covey
2007-06-17 20:30 ` William Morgan
2007-06-18 1:00 ` jeff covey
2007-07-10 18:21 ` William Morgan [this message]
2007-08-30 19:50 ` jeff covey
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=1184091559-sup-1633@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