From: vasudeva@linkswarm.com (vasudeva)
Subject: [sup-talk] sup-sync-back reports: Nothing to do
Date: Thu, 21 Feb 2008 19:17:11 -0500 [thread overview]
Message-ID: <1203639414-sup-3734@lenin> (raw)
I seem to be unable to run sup-sync-back to apply my sup-world changes
back to my mbox file...
**
ruby -I /home/vasudeva/sup/lib -w /home/vasudeva/sup/bin/sup-sync-back mbox:///home/vasudeva/muttmail/inbox
/home/vasudeva/sup/lib/sup/util.rb:8: warning: method redefined; discarding old gen_lock_id
/home/vasudeva/sup/lib/sup/util.rb:19: warning: method redefined; discarding old dump_lock_id
[Thu Feb 21 17:34:46 -0500 2008] using character set encoding "UTF-8"
/home/vasudeva/sup/lib/sup/message-chunks.rb:36: warning: method
redefined; discarding old make_tmpname
/var/lib/gems/1.8/gems/chronic-0.2.3/lib/chronic/repeaters/repeater_month_name.rb:13: warning: useless use of > in void context
/var/lib/gems/1.8/gems/chronic-0.2.3/lib/chronic/repeaters/repeater_month_name.rb:19: warning: useless use of > in void context
/var/lib/gems/1.8/gems/chronic-0.2.3/lib/chronic/repeaters/repeater_month_name.rb:25: warning: useless use of < in void context
Nothing to do.
**
There are definitely changes that need to be applied; enough that I
think there may be some kind of index desynching going on.
I'm not terribly worried about it, since it'll take 10 minutes to re-do
those changes manually to my mbox, but I thought it was kind of an
interesting oddity, and might shed some light on something worthwhile if
anyone's bored.
I've tried against the newest master and next; same deal.
--
linkswarm.com :: Collaborative Insolence
vasudeva.linkswarm.com/gallery :: For The Faint of Heart
next reply other threads:[~2008-02-22 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 0:17 vasudeva [this message]
2008-02-25 17:17 ` William Morgan
2008-02-25 17:53 ` vasudeva
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=1203639414-sup-3734@lenin \
--to=vasudeva@linkswarm.com \
/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