9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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
Date: Mon,  9 Apr 2007 11:44:23 -0400	[thread overview]
Message-ID: <9ab217670704090844g4a719e9cgc0c6b965338f79f5@mail.gmail.com> (raw)
In-Reply-To: <160b8b18ca5720d6144ba0b9e75c0b30@coraid.com>

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


  reply	other threads:[~2007-04-09 15:44 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 15:32 erik quanstrom
2007-04-09 15:44 ` Devon H. O'Dell [this message]
2007-04-09 16:15   ` Martin Neubauer
  -- strict thread matches above, loose matches on Subject: below --
2007-04-09 16:23 erik quanstrom
2007-04-05 19:45 pedro henrique antunes de oliveira
2007-04-05 21:15 ` John Floren
2007-04-05 21:56   ` W B Hacker
2007-04-05 21:57   ` geoff
2007-04-09 14:24     ` Benn Newman
2007-04-09 14:50       ` Devon H. O'Dell
2007-04-09 14:55         ` erik quanstrom
2007-04-09 15:08           ` Devon H. O'Dell
2007-04-09 15:24             ` erik quanstrom
2007-04-09 15:40               ` Devon H. O'Dell
2007-04-09 15:01         ` Devon H. O'Dell
2007-04-09 15:22         ` ron minnich
2007-04-09 15:30           ` Devon H. O'Dell
2007-04-09 18:02             ` ron minnich
2007-04-09 18:11               ` geoff
2007-04-09 18:14                 ` andrey mirtchovski
2007-04-09 21:04                   ` ron minnich
2007-04-09 22:01               ` Paweł Lasek
2007-04-09 23:26           ` Kris Maglione
2007-04-10  0:14             ` ron minnich
2007-04-10  0:15             ` erik quanstrom
2007-04-10  0:41               ` Uriel
2007-04-10  7:57                 ` Francisco J Ballesteros
2007-04-10  1:08               ` Kris Maglione
2007-04-09 15:50         ` Russ Cox
2007-04-09 16:18           ` Devon H. O'Dell
2007-04-09 16:46             ` matt
2007-04-09 17:51             ` Russ Cox
2007-04-09 17:07           ` Uriel
2007-04-09 17:11             ` Devon H. O'Dell
2007-04-09 17:32               ` Uriel
2007-04-09 18:03                 ` ron minnich
2007-04-09 18:07                   ` Devon H. O'Dell
2007-04-09 23:03                   ` Christopher Nielsen
2007-04-05 21:27 ` W B Hacker
2007-04-05 21:33   ` pedro henrique antunes de oliveira
2007-04-05 21:49     ` Fazlul Shahriar
2007-04-05 21:51       ` pedro henrique antunes de oliveira

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=9ab217670704090844g4a719e9cgc0c6b965338f79f5@mail.gmail.com \
    --to=devon.odell@gmail.com \
    --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).