9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] VCS on Plan9
Date: Thu, 18 Apr 2024 17:40:05 -0400	[thread overview]
Message-ID: <CAEoi9W6Vq_svgzQ2fNma9ifpfQSzBTAp-a=gX_0Gw+=gZOEOfA@mail.gmail.com> (raw)
In-Reply-To: <18666890-3753-4B73-864F-C6EFEEFC392B@quintile.net>

On Thu, Apr 18, 2024 at 5:01 PM Steve simon <steve@quintile.net> wrote:
> re: VCS -vs-dump
>
> I always planned to add code to fossil to allow members of (say) the 'dump' group to trigger fa fossil to venti dump at arbitrary times.
> If with this it would be trivial to have a 'release' rc script which could save a log message and trigger a dump.

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?

> I know this is not really a VCS but the ability to get back to an atomic set of files representing a release would help a lot IMHO.

I could see the utility in that, but at this point, a repo in some
modern VCS that contained the source combined with a snapshot of the
release contents (containing binaries and so on) would be better,
IMHO.

Ironically, this came full circle for me a decade or so ago at Google.
I was explaining Venti to someone and they said, "why did they write
that? Why not just write to git?" I had to explain that Venti predated
`git` by several years. Kids these days!

        - Dan C.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tab2715b0e6f3e0a5-M13b4db40706f74184c419de7
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2024-04-18 21:40 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 [this message]
2024-04-19  4:09           ` ori
2024-04-19 14:01             ` Dan Cross
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='CAEoi9W6Vq_svgzQ2fNma9ifpfQSzBTAp-a=gX_0Gw+=gZOEOfA@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).