From: Nicolas Bercher <nbercher@yahoo.fr>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] can't access fossil dumps anymore
Date: Fri, 10 Jun 2011 22:03:42 +0200 [thread overview]
Message-ID: <4DF2789E.8010706@yahoo.fr> (raw)
In-Reply-To: <20110609132848.183d1cf5@wks-ddc.exosec.local>
On 09/06/2011 13:28, David du Colombier wrote:
>> - How do I achieve this? (via fossilcons?)
>
> If you really want to do this, keep in mind you will lose
> all your data on your fossil partition. You will definitely
> lose all the temporary snapshots and all data not archived
> to venti.
First of all, thank you for theses clear explanations (typically the one I need as a
beginner). Does your answer implicitly means that this is the solution to the fossil
message "block label mismatch"?
Nicolas
next prev parent reply other threads:[~2011-06-10 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 22:13 Nicolas BERCHER
2011-06-09 11:28 ` David du Colombier
2011-06-10 20:03 ` Nicolas Bercher [this message]
2011-06-10 20:42 ` David du Colombier
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=4DF2789E.8010706@yahoo.fr \
--to=nbercher@yahoo.fr \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).