From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] replica
Date: Thu, 4 Jul 2002 19:16:26 +0900 [thread overview]
Message-ID: <20020704101716.AA93F19988@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
Can replica/pull -n see the changes after I updated the changes?
I updated too many files in a long time, so I came off the desk, and did
other obligations I have for money. If I could have some backup files
for locally changed ones, I can check it later, and give enough time to
do that...
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 3889 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 206 bytes --]
I do a replica/pull -n to see the changes,
then I use diff or acme to look at what changed if I'm not willing
to pull them without looking first at them.
perhaps this may achieve the effect you want.
[-- Attachment #2.1.2: Type: message/rfc822, Size: 1762 bytes --]
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] replica
Date: Thu, 4 Jul 2002 18:21:37 +0900
Message-ID: <20020704092234.344EE19988@mail.cse.psu.edu>
Don't laugh me even though I was much delayed to see replica(1). ^_^
Yeah! Replica is very nice interface to maintain and distribute solid
trees of Plan 9. Thanks everyone who have worked for it.
I have one request here.
When I have some local change to a file, replica reports it without telling me
what was changed in the replica server. Sometime, I want to know what was
changed at Labs, because I have no such solid confidence to myself in many
case. ;_;
May I ask you to put the changed file of the replica server to my local disk
with modifying the name, say such kenji.c to kenji.c.p9bell?
Kenji
next reply other threads:[~2002-07-04 10:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 10:16 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-25 2:30 Richard Bilson
2006-08-25 3:38 ` Lyndon Nerenberg
2006-08-25 4:08 ` geoff
2006-08-25 8:19 ` Martin Neubauer
2006-08-27 23:23 ` geoff
2006-08-28 2:46 ` Richard Bilson
2005-02-12 13:42 Sergey Reva
2005-02-12 16:15 ` Russ Cox
2004-03-24 13:20 David Presotto
2002-07-30 12:15 Russ Cox
2002-07-04 10:20 Fco.J.Ballesteros
2002-07-04 9:26 Fco.J.Ballesteros
2002-07-04 9:21 okamoto
2002-05-29 16:32 Russ Cox
2002-05-29 9:43 forsyth
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=20020704101716.AA93F19988@mail.cse.psu.edu \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).