From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pull
Date: Thu, 9 Oct 2003 17:23:06 +0200 [thread overview]
Message-ID: <403d6f1f1c645461d13d6f9dec16e023@plan9.escet.urjc.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0310090915200.2724-100000@maxroach.lanl.gov>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
We use this script (in our /rc/bin/pull).
The magic I mention is whatever you have to do to convince
your fossil to allow wstats and ignore permissions for the
changes made while pulling. We use the allow command
we added to fossil, but you may have to import a connection
that has been created to allow such things.
#!/bin/rc
rfork ne
*** ADD HERE YOUR MAGIC to put fossil into allow mode
opt=()
clean=no
while(! ~ $#* 0 && ~ $1 -*){
if (~ $1 -C)
clean=yes
if not
opt=($opt $1)
shift
}
if(~ $1 --)
shift
replica/pull -v $opt /dist/replica/network $*
*** ADD HERE YOUR MAGIC to put fossil out off allow mode
exit ''
[-- Attachment #2: Type: message/rfc822, Size: 2417 bytes --]
From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] pull
Date: Thu, 9 Oct 2003 09:16:26 -0600 (MDT)
Message-ID: <Pine.LNX.4.44.0310090915200.2724-100000@maxroach.lanl.gov>
I've done some looking around but it's not clear how I use 'pull' to a
fossil. The basic command gets lots of kfs errors, since there is no kfs.
Is this the usual pilot error on my part or is it just not ready yet?
thanks
ron
next prev parent reply other threads:[~2003-10-09 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 15:16 ron minnich
2003-10-09 15:23 ` Fco.J.Ballesteros [this message]
2003-10-09 15:32 ` mirtchov
2006-01-28 20:22 [9fans] pull - read this! Russ Cox
2006-01-31 18:28 ` [9fans] pull Heiko Dudzus
2006-01-31 18:55 ` Russ Cox
2006-02-03 18:40 Heiko Dudzus
2006-04-06 1:50 Eric Smith
2006-04-06 8:14 ` Lluís Batlle
2006-04-06 15:19 ` Russ Cox
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=403d6f1f1c645461d13d6f9dec16e023@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).