From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Sam: m and "changes not in sequence"
Date: Wed, 9 May 2007 16:18:43 +0100 [thread overview]
Message-ID: <f998342120511f9fa05ba8af48f95bc6@vitanuova.com> (raw)
In-Reply-To: <46400475.CD8IinOH3SQR21Fj%yard-ape@telus.net>
> In Sam, I tried variations of:
>
> x g/foobar/m0
>
> but consistently received "changes not in sequence" errors.
try
,|tail -r
prev parent reply other threads:[~2007-05-09 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 5:57 [9fans] Error booting from latest plan9.iso download Wes
2007-05-07 6:02 ` Federico Benavento
2007-05-07 6:04 ` Wes
2007-05-07 6:53 ` Wes
2007-05-07 8:35 ` Martin Neubauer
2007-05-07 10:11 ` Federico Benavento
2007-05-08 0:10 ` Wes
2007-05-08 5:02 ` [9fans] Sam: m and "changes not in sequence" Yard Ape
2007-05-08 19:18 ` Micah Stetson
2007-05-09 15:18 ` rog [this message]
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=f998342120511f9fa05ba8af48f95bc6@vitanuova.com \
--to=rog@vitanuova.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).