9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] hgfs
Date: Thu, 22 May 2014 08:35:33 -0700	[thread overview]
Message-ID: <CAJSxfmK-Eopfn3+eHhrcHsSDJ7g-YCMFu8RZqStd0FPCh9r2Uw@mail.gmail.com> (raw)
In-Reply-To: <CAEAzY39-Q_j0uo5qRVL2E-O8mYVtzr2R-GTGOU-xfx5C=xoG1A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]

On Thu, May 22, 2014 at 3:41 AM, Aram Hăvărneanu <aram.h@mgk.ro> wrote:

> Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
> > % cat /n/hg/versions  # list versions
> > ...
> > % echo version rev1 > /n/hg/ctl # pull + update -r rev1, etc.
> > % ls /n/hg/foo
> > .... # list of rev1 files
> > % echo version rev2 > /n/hg/ctl
> > % ls /n/hg/foo
> > ... # list of rev2 files, etc
>
> What would be the point of this? Once you have a version (revision)
> you can just bind the subtree where you want it. I don't see the
> point in having this special switching code inside hgfs. Plan 9
> provides the necessary functionality.
>

true, but now you'd have to have another layer of scripts, etc. why not
just make it look the way it should?


>
> > % ed /n/hg/foo/main.c <<'EOF'
> > $a
> > // a useless comment
> > .
> > w
> > q
> > EOF
> > % cat <<'EOF' >/n/hg/ctl
> > tag "rev1beta1"  # tag this version
> > note "added a silly comment to main.c and tagged this version
> > as beta1" # commit string?
>
> Somebody would have to write the code, right now hgfs is read-only.
> I don't know how hard it would be. Are you offering?
>
>
i've been thinking about this (as obviously others have been too -- see
Bakul's post on another thread), but since i don't have enough rope at the
moment to fathom the depths of hg and git, i'm offering it for comment or
dare :)

-Skip

--
> Aram Hăvărneanu
>
>

[-- Attachment #2: Type: text/html, Size: 2482 bytes --]

  reply	other threads:[~2014-05-22 15:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22  6:52 Skip Tavakkolian
2014-05-22  7:36 ` lucio
2014-05-22  9:54   ` Aram Hăvărneanu
2014-05-22 10:30     ` lucio
2014-05-22 10:41 ` Aram Hăvărneanu
2014-05-22 15:35   ` Skip Tavakkolian [this message]
2014-05-22 15:56     ` erik quanstrom
2014-05-22 16:17       ` ron minnich
2014-05-22 16:21         ` Kurt H Maier
2014-05-22 16:31         ` Aram Hăvărneanu
2014-05-22 18:37           ` ron minnich
2014-05-22 18:45             ` Kurt H Maier
2014-05-22 18:51             ` Aram Hăvărneanu
2014-05-22 19:02               ` Latchesar Ionkov
2014-05-22 19:13                 ` Kurt H Maier
2014-05-22 19:16                   ` erik quanstrom
2014-05-22 19:23                   ` Latchesar Ionkov
2014-05-23  3:45                     ` hiro
2014-05-22 19:11               ` Skip Tavakkolian
2014-05-22 19:23         ` Bakul Shah
2014-05-22 19:47         ` Skip Tavakkolian
2014-05-22 16:20       ` lucio
2014-05-22 19:46   ` Bakul Shah
  -- strict thread matches above, loose matches on Subject: below --
2011-06-27  5:43 cinap_lenrek
2011-06-27 13:15 ` hiro
2011-06-27  5:09 cinap_lenrek

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=CAJSxfmK-Eopfn3+eHhrcHsSDJ7g-YCMFu8RZqStd0FPCh9r2Uw@mail.gmail.com \
    --to=skip.tavakkolian@gmail.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).