From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup crashes on startup
Date: Wed, 27 Jan 2010 08:21:23 -0500 [thread overview]
Message-ID: <1264598438-sup-499@masanjin.net> (raw)
In-Reply-To: <8b854d6b1001270451q430c1176t775b77e1e127df26@mail.gmail.com>
Reformatted excerpts from Shreyank Gupta's message of 2010-01-27:
> This Sup version expects a v1 index, but you have an existing v2
> index. Please downgrade to your previous version and dump your labels
> before upgrading to this version (then run sup-sync --restore).
You used git next before, and now you're trying git master. There is a
version incompatibility that will go away once a particular topic branch
gets merged down to master.
Workaround: use git next for now.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-01-27 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 12:51 Shreyank Gupta
2010-01-27 12:59 ` Ben Walton
2010-01-27 13:21 ` William Morgan [this message]
2010-01-27 15:03 ` Shreyank Gupta
-- strict thread matches above, loose matches on Subject: below --
2008-03-28 22:13 [sup-talk] sup " Martin DeMello
2008-04-01 15:04 ` William Morgan
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=1264598438-sup-499@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox