From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
From: nemo@plan9.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil/flfmt -v problem
Date: Fri, 4 Jul 2003 15:37:33 +0200 [thread overview]
Message-ID: <c67f11000dd2c24b69bac8e6d6f48c16@plan9.escet.urjc.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0307032235070.19955-100000@fbsd.cpsc.ucalgary.ca>
> I saw the scripts (lastfossil and vacchain) however they don't help me much,
> since 'fossil/flfmt -v' with a wrong score destroyed my fossil partition.
I have a cron that prints (daily) the vacchain. Is there a better way?
This is also what you're asking, if I understood correctly.
next prev parent reply other threads:[~2003-07-04 13:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 22:50 andrey mirtchovski
2003-07-04 3:23 ` jmk
2003-07-04 3:35 ` andrey mirtchovski
2003-07-04 3:57 ` jmk
2003-07-04 4:37 ` andrey mirtchovski
2003-07-04 13:37 ` Fco.J.Ballesteros, nemo [this message]
2003-07-04 13:51 ` andrey mirtchovski
2003-07-04 16:42 ` jmk
2003-07-04 17:17 ` Fco.J.Ballesteros, nemo
2003-07-04 17:21 ` rog
2003-07-04 17:20 ` Fco.J.Ballesteros, nemo
2003-07-04 17:25 ` Fco.J.Ballesteros, nemo
2003-07-04 17:46 ` rog
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=c67f11000dd2c24b69bac8e6d6f48c16@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/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).