9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] broken vac
Date: Mon,  3 Feb 2003 09:53:00 -0500	[thread overview]
Message-ID: <bd9e466e688a7df4a8578e8781621ecc@plan9.bell-labs.com> (raw)
In-Reply-To: <c3c0894654e5b89c4a1346075c3167cf@vitanuova.com>

did you do a pull while you were running that vac?
if so, it may have broken just because the text file
changed underneath it and it got confused when it
paged in a new section.




  reply	other threads:[~2003-02-03 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 14:53 rog
2003-02-03 14:53 ` Russ Cox [this message]
2003-02-03 15:36   ` Axel Belinfante
2003-02-03 15:50     ` Russ Cox
2003-02-03 17:17     ` Fco.J.Ballesteros
  -- strict thread matches above, loose matches on Subject: below --
2003-01-31 15:08 Axel Belinfante
2003-01-31 16:23 ` Fco.J.Ballesteros
2003-01-31 16:33   ` Russ Cox
2003-01-31 18:37     ` Axel Belinfante
2003-01-31 18:52       ` Axel Belinfante
2003-01-31 18:57         ` Russ Cox
2003-01-31 16:23 ` Fco.J.Ballesteros

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=bd9e466e688a7df4a8578e8781621ecc@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.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).