From: marcus-sup@quintic.co.uk
To: sup-devel@rubyforge.org
Subject: Re: [sup-devel] [issue74] sup-dump producing empty file in latest release
Date: Tue, 09 Mar 2010 09:48:05 +0000 [thread overview]
Message-ID: <4B961955.7000306@quintic.co.uk> (raw)
In-Reply-To: <1268089517.99.0.931999852916.issue74@masanjin.net>
On 08/03/2010 23:05, anonymous wrote:
> sup-dump produces an empty dump file with git next (0.11 is probably closest
> release). I updated this morning after the release announcement and started the
> process to switch to xapian. Luckily I checked the dumpfile produced because it
> turned out empty:(
I reported this, so if any more information is needed I'm on this list
(and obviously I'm tracking it in the issue tracker).
Marcus
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-03-09 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 23:05 anonymous
2010-03-09 9:48 ` marcus-sup [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=4B961955.7000306@quintic.co.uk \
--to=marcus-sup@quintic.co.uk \
--cc=sup-devel@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