From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9ab217670704090844g4a719e9cgc0c6b965338f79f5@mail.gmail.com>
Date: Mon,  9 Apr 2007 11:44:23 -0400
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] bell-labs website and plan9
In-Reply-To: <160b8b18ca5720d6144ba0b9e75c0b30@coraid.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <160b8b18ca5720d6144ba0b9e75c0b30@coraid.com>
Topicbox-Message-UUID: 41b26288-ead2-11e9-9d60-3106f5b1d025

2007/4/9, erik quanstrom <quanstro@coraid.com>:
> > available? It'd save me some time and effort trying to figure out how
> > to revert a replica/pull.
> >
> > Speaking of which, how _does_ one replica/pull to a previous date?
> >
> > --dho
>
> there are lots of ways to do this, but a particular senerio would be helpful.
> for example, if you wanted to pull only up to date x, then you could just edit
> the log and delete entries that come later.  you can always mount sourcesdump
> and either copy or mount what you'd like if you have a problem with a particular
> package.
>
> - erik

The scenario being, I want to test my hypothetical replica/applylog
action parser / diff generator. I run pull, which grabs stuff, but
I've made changes to xyz.c and that file doesn't get modified because
of local changes. So I want to roll back my log so I can run pull
again with -s /sys/src/cmd/xyz.c

This wouldn't be an issue if we added a '*' option to replica/pull for
the -c and -s flags. But I'll send a patch for that shortly and see if
that gets committed.

--dho