From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] hgfs
Date: Wed, 21 May 2014 23:52:38 -0700 [thread overview]
Message-ID: <CAJSxfmJRpLxjU3HEOjJCBqzVc5wUoOBxc=uJhn41oOxA3a5yVQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
i'm playing with hgfs. here are some first observations/thoughts.
for a given repository foo, if the repository mounted on /n/hg, had a
hierarchy like:
/n/hg
/ctl
/versions
/foo
it would feel more natural if i could do:
% 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
% 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?
push # push the changes upstream, etc.
EOF
etc.
it would be nice to map as many hg/git operations to file operations as
possible. for the rest providing special files (ctl, versions, etc) and
directives don't seem out of place.
[-- Attachment #2: Type: text/html, Size: 1456 bytes --]
next reply other threads:[~2014-05-22 6:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 6:52 Skip Tavakkolian [this message]
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
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='CAJSxfmJRpLxjU3HEOjJCBqzVc5wUoOBxc=uJhn41oOxA3a5yVQ@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).