9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx is really excellent, link it on the bell-labs pages?
Date: Wed, 30 Sep 2009 10:55:42 -0700	[thread overview]
Message-ID: <dd6fe68a0909301055h1fbbf1cbh2abd443c0a7c9b6b@mail.gmail.com> (raw)
In-Reply-To: <13426df10909300955n1a62aab5o9f137d533112e01a@mail.gmail.com>

> Now I have to confess I can't recall how to print all the thread
> callback stacks when 9vx breaks, not having had to do it for a year or
> so but ... I'm happy to set up a gdb for it and do what commands are
> needed should it break. Any recommendations here Russ?

thread apply all where
is the gdb command to get all stack traces.

> One other question -- anybody know how to create a 'tracking fork' in
> mercurial such that I can fork 9vx, but update from Russ's version to
> mine over time? I have some things I want to try out. I have not found
> a way to do this  yet. The reason to do this "private repo" would be
> to have some other place to store my experiments than my laptop ...

Every checkout in Mercurial is a fork like that.
The easiest setup is to pick one such checkout
to be your coordination point.

    hg clone http://code.swtch.com/vx32/ vx32-main

Then you can clone vx32-main and push to
and pull from it.  When you want to update you
go into vx32-main and run hg pull, merge, and
then re-pull from your various clones.

If you are on another machine from where vx32-main
is, you can clone it with

    hg clone ssh://kremvax//home/rminnich/vx32-main

Russ


      reply	other threads:[~2009-09-30 17:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30  8:23 Sam Watkins
2009-09-30 14:45 ` David Leimbach
2009-09-30 15:30   ` Ethan Grammatikidis
2009-09-30 16:16     ` matt
2009-09-30 16:54       ` matt
2009-10-01  0:32         ` Ethan Grammatikidis
2009-09-30 16:55       ` ron minnich
2009-09-30 17:55         ` Russ Cox [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=dd6fe68a0909301055h1fbbf1cbh2abd443c0a7c9b6b@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.net \
    /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).