From: Matthias Teege <matthias@mteege.de>
To: 9fans@cse.psu.edu
Subject: [9fans] update via replica/pull
Date: Wed, 24 Mar 2004 16:35:42 +0000 [thread overview]
Message-ID: <e002c15189db60461e270f14d504c3b7@mteege.de> (raw)
Moin,
I try to update from sources but I'm not sure about the
procedure. Is
9fs sources
bind /n/sources/plan9 /n/dist
replica/pull -v /n/dist
what I'm looking for?
What about permissions and users? Can I do this as "normal"
user? I use an non fossil fileserver. Is it necessary to turn off
the permission checking on the fileserver? After replica/pull,
which parts should be rebuild? Is there somthing like "make
world"?
Many thanks
Matthias
next reply other threads:[~2004-03-24 16:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 16:35 Matthias Teege [this message]
2004-03-24 16:48 ` andrey mirtchovski
2004-03-24 16:53 ` Russ Cox
2004-03-24 17:13 ` Matthias Teege
2004-03-24 17:32 ` Skip Tavakkolian
2004-03-25 6:10 ` Matthias Teege
2004-03-25 6:13 ` Charles Forsyth
2004-03-24 17:33 ` Steve Simon
2004-03-24 23:52 ` Geoff Collyer
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=e002c15189db60461e270f14d504c3b7@mteege.de \
--to=matthias@mteege.de \
--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).