From: Dan Cross <crossd@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] VCS on Plan9
Date: Fri, 19 Apr 2024 10:01:36 -0400 [thread overview]
Message-ID: <CAEoi9W619tJ-N-EHkirTZ1FdRBYrGxHhsa=n19T9aj3=vuGSZw@mail.gmail.com> (raw)
In-Reply-To: <E27BB4ED060D9AFD931420907267BD12@eigenstate.org>
On Fri, Apr 19, 2024 at 12:10 AM <ori@eigenstate.org> wrote:
> Quoth Dan Cross <crossd@gmail.com>:
> > Correct me if I'm wrong, but this is just an `echo` into fossilcons,
> > isn't it? `fsys main snap -a` or something like it?
>
> it would be if being able to write to fossilcons
> didn't imply being able to do a lot more than
> creating a new snapshot.
Fair point. But it would be pretty simple to write a small proxy
service that wrapped that, and only exposed something that let an
authorized user trigger writing the `snap` command into `fossilcons`
on one's behalf. The point is, the raw tools to do what Steve proposed
mostly already exist; wiring them up shouldn't require any changes to
fossil itself.
This is all rather far afield from the issue of revision control,
though. Getting back to that, a true VCS and the sort of backup
facility offered by fossil+venti (and other similar things, such as
the work you've done on filesystems) are mostly orthogonal.
- Dan C.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tab2715b0e6f3e0a5-M4869765d772e9c6a4d5a5d32
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2024-04-19 14:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 15:54 certanan via 9fans
2024-04-18 16:02 ` Jacob Moody
2024-04-18 16:05 ` certanan via 9fans
2024-04-18 16:11 ` Paul Lalonde
2024-04-18 20:26 ` Bakul Shah via 9fans
2024-04-18 20:41 ` Dan Cross
2024-04-18 21:00 ` Steve simon
2024-04-18 21:40 ` Dan Cross
2024-04-19 4:09 ` ori
2024-04-19 14:01 ` Dan Cross [this message]
2024-04-18 21:48 ` Shawn Rutledge
2024-04-18 23:17 ` Bakul Shah via 9fans
2024-04-18 23:52 ` Dan Cross
2024-04-19 0:09 ` Jacob Moody
2024-04-18 23:15 ` Bakul Shah via 9fans
2024-04-20 8:30 ` Giacomo Tesio
2024-04-20 19:11 ` Dan Cross
2024-04-18 16:34 ` cinap_lenrek
2024-04-18 16:47 ` Dave Eckhardt
2024-04-19 9:07 ` Edouard Klein
2024-04-19 9:34 ` Stuart Morrow
2024-04-18 20:08 ` Ori Bernstein
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='CAEoi9W619tJ-N-EHkirTZ1FdRBYrGxHhsa=n19T9aj3=vuGSZw@mail.gmail.com' \
--to=crossd@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).