From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 22 May 2014 08:35:33 -0700 Message-ID: From: Skip Tavakkolian To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a113487741d15cc04f9fedd2b Subject: Re: [9fans] hgfs Topicbox-Message-UUID: ede114fe-ead8-11e9-9d60-3106f5b1d025 --001a113487741d15cc04f9fedd2b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, May 22, 2014 at 3:41 AM, Aram H=C4=83v=C4=83rneanu = wrote: > Skip Tavakkolian 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=C4=83v=C4=83rneanu > > --001a113487741d15cc04f9fedd2b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Thu, May 22, 2014 at 3:41 AM, Aram H=C4=83v=C4=83rneanu <aram.h@mgk.ro<= /a>> wrote:
Skip Tavakkolian <skip.tavakkolian@gmail.com> w= rote:
> % cat /n/hg/versions =C2=A0# 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.

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

> % ed /n/hg/foo/main.c <<'EOF'
> $a
> // a useless comment
> .
> w
> q
> EOF
> % cat <<'EOF' >/n/hg/ctl
> tag "rev1beta1" =C2=A0# 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 othe= rs have been too -- see Bakul's post on another thread), but since i do= n'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=C4=83v=C4=83rneanu


--001a113487741d15cc04f9fedd2b--