Re: [9fans] VCS on Plan9

On Sat, Apr 20, 2024 at 4:31 AM Giacomo Tesio wrote: > Hi 9fans > > Il 18 Aprile 2024 22:41:50 CEST, Dan Cross ha scritto: > > > > Git and Jujitsu are, frankly, superior > > out of curiosity, to your knowedge, did anyone ever tried to port fossil > scm > to Plan9 or 9front (even through ape)? >

Re: [9fans] VCS on Plan9

Hi 9fans Il 18 Aprile 2024 22:41:50 CEST, Dan Cross ha scritto: > > Git and Jujitsu are, frankly, superior out of curiosity, to your knowedge, did anyone ever tried to port fossil scm to Plan9 or 9front (even through ape)? Also

Re: [9fans] VCS on Plan9

On Fri, Apr 19, 2024 at 12:10 AM wrote: > Quoth Dan Cross : > > 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 >

Re: [9fans] VCS on Plan9

On Fri, 19 Apr 2024 at 10:09, Edouard Klein wrote: > I love it when I discover that something down on my todo-list has > already been done, [ ... > ... ] > > https://9p.io/wiki/plan9/divergefs/ It's been done *twice*: https://git.sr.ht/~kvik/unionfs --

Re: [9fans] VCS on Plan9

I love it when I discover that something down on my todo-list has already been done, better than I would have, by someone else :) Very neat tool, I'll be using it soon. Dave Eckhardt writes: >> One thing i did was sometimes to create a skeletron directory >> tree and bind *before* each single

Re: [9fans] VCS on Plan9

Quoth Dan Cross : > > 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.

Re: [9fans] VCS on Plan9

On 4/18/24 16:48, Shawn Rutledge wrote: > Interesting that it's Rust.  Just another reason to eventually have Rust on > Plan 9… Has anyone done any work on this? I know someone technically got stuff running using a webasm intermediate, but I am curious if anyone has scoped out what it would

Re: [9fans] VCS on Plan9

On Thu, Apr 18, 2024, 7:18 PM Bakul Shah via 9fans <9fans@9fans.net> wrote: > On Apr 18, 2024, at 2:48 PM, Shawn Rutledge wrote: > > > Just another reason to eventually have Rust on Plan 9… > > > Yeah. Compiles are too damn fast; no time to make masala chai :-) > Arrey yaar, miri vo ki bahoat

Re: [9fans] VCS on Plan9

On Apr 18, 2024, at 2:48 PM, Shawn Rutledge wrote: > > Just another reason to eventually have Rust on Plan 9… Yeah. Compiles are too damn fast; no time to make masala chai :-) -- 9fans: 9fans Permalink:

Re: [9fans] VCS on Plan9

On Apr 18, 2024, at 1:41 PM, Dan Cross wrote: > > Culturally, there was a feeling that source revision a la RCS, SCCS, > etc, were unnecessary because the dump filesystem gave you snapshots > already. Moreover, those were automatic and covered more than one file > at a time; RCS/SCCS required

Re: [9fans] VCS on Plan9

> On Apr 18, 2024, at 1:41 PM, Dan Cross wrote: > > Git and Jujitsu are, frankly, superior. Aha, I had never heard of Jujutsu until now; you mean https://martinvonz.github.io/jj/ right? Monitoring file changes and treating changes to the working copy as an implicit work-in-progress commit

Re: [9fans] VCS on Plan9

On Thu, Apr 18, 2024 at 5:01 PM Steve simon 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 >

Re: [9fans] VCS on Plan9

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. I know this is not really

Re: [9fans] VCS on Plan9

On Thu, Apr 18, 2024 at 4:27 PM Bakul Shah via 9fans <9fans@9fans.net> wrote: > Did anyone try to port sccs to plan9? Interesting question; I suspect not. The only reason to have done so would have been to inspect source repositories created outside of plan 9, in which case it likely would have

Re: [9fans] VCS on Plan9

Did anyone try to port sccs to plan9? > On Apr 18, 2024, at 9:11 AM, Paul Lalonde wrote: > > The Bell Labs approach to source control was, I'm, weak. It relied on > snapshots of the tree and out-of-band communication. Don't forget how small > and tight-knit that development team was, and

Re: [9fans] VCS on Plan9

On Thu, 18 Apr 2024 15:54:07 + "certanan via 9fans" <9fans@9fans.net> wrote: > Hi, > > is there any more "organic/natural" way to do source control on today's Plan9 > (9front specifically), other than Ori's Git? on today's plan 9? no. > > In other words, how (if at all) did people at

Re: [9fans] VCS on Plan9

> One thing i did was sometimes to create a skeletron directory > tree and bind *before* each single directory in /sys/src/9. > > when i needed to modify a file, you copy it in your "overlay" > tree. https://9p.io/wiki/plan9/divergefs/ Dave Eckhardt --

Re: [9fans] VCS on Plan9

One thing i did was sometimes to create a skeletron directory tree and bind *before* each single directory in /sys/src/9. when i needed to modify a file, you copy it in your "overlay" tree. not exactly version control, but a primitive way to prepare a change. -- cinap

Re: [9fans] VCS on Plan9

The Bell Labs approach to source control was, I'm, weak. It relied on snapshots of the tree and out-of-band communication. Don't forget how small and tight-knit that development team was, and how valuable perfect historic snapshots were. Add that 40 years ago source code revision control

Re: [9fans] VCS on Plan9

> From what I understand folks used to make diffs against the last release. > There was also some use of replica as you eluded to. That answers my question. Thanks. tom -- 9fans: 9fans Permalink:

Re: [9fans] VCS on Plan9

On 4/18/24 10:54, certanan via 9fans wrote: > Hi, > > is there any more "organic/natural" way to do source control on today's Plan9 > (9front specifically), other than Ori's Git? > > In other words, how (if at all) did people at Bell Labs and the community > alike originally manage their

[9fans] VCS on Plan9

Hi, is there any more "organic/natural" way to do source control on today's Plan9 (9front specifically), other than Ori's Git? In other words, how (if at all) did people at Bell Labs and the community alike originally manage their contributions in a way that would allow them to create patches