From: Heiko Dudzus <heiko.dudzus@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pull
Date: Fri, 3 Feb 2006 19:40:20 +0100 [thread overview]
Message-ID: <440879660de56a030cadd74423b90608@voidness.de> (raw)
> You can ignore this message if you want, but I print it to make
> you wonder what's going on. In this case, you should probably
> be running
>
> replica/pull -v -c 386/9pcf /dist/replica/network
>
> which will pull any files except skip past changes to 386/9pcf.
>
> What you typed:
>
> replica/pull -v -c 386/9pcf /dist/replica/network 386/9pcf
>
> will not pull any changes. It says "pull only files matching 386/9pcf
> (the last argument) but whenever you see a change to 386/9pcf,
> ignoring it in favor of the local version (the -c option)."
It's getting clearer to me. What I wanted to say was: "Keep your eyes
on conflicts with 386/9pcf and resolve them with the clients version."
> At any point in time, replica/pull knows how much of
> /dist/replica/client/plan9.log it has successfully applied and
> can ignore on the next run. It stores this information in
> /dist/replica/client/plan9.time. Plan9.log is applied up to and
> including the line that begins with the numbers in plan9.time.
Ok. Thanks for the explanation.
Heiko
next reply other threads:[~2006-02-03 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 18:40 Heiko Dudzus [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-06 1:50 Eric Smith
2006-04-06 8:14 ` Lluís Batlle
2006-04-06 15:19 ` Russ Cox
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
2003-10-09 15:16 ron minnich
2003-10-09 15:23 ` Fco.J.Ballesteros
2003-10-09 15:32 ` mirtchov
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=440879660de56a030cadd74423b90608@voidness.de \
--to=heiko.dudzus@gmx.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).