From: Jacob Moody <moody@posixcafe.org>
To: certanan via 9fans <9fans@9fans.net>
Subject: Re: [9fans] VCS on Plan9
Date: Thu, 18 Apr 2024 11:02:51 -0500 [thread overview]
Message-ID: <17b1d3d2-8ad2-4a53-aa65-ef42b26bbd33@posixcafe.org> (raw)
In-Reply-To: <UBa1C0_P8Q-Jc86_hqhPwhv2h6a3fZxFXwbOYSqWBqyGSS5uVujUNHXU-0a_xOgtwvJammzjwCc2cLugrvZS2pguCb1O9_HCqZd1Xop6Eic=@proton.me>
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 contributions in a way that would allow them to create patches without much hassle?
>
> Was it as simple as backing a source tree up, making some changes, and then comparing the two? Venti? Replica?
Perhaps worth mentioning that before git 9front used mecurial for VCS, but I don't think that answers your question.
From what I understand folks used to make diffs against the last release. There was also some use of replica as you eluded to.
Thanks,
moody
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tab2715b0e6f3e0a5-M9dd2ab1b9959fd2af34615b8
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2024-04-18 16:03 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 [this message]
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
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=17b1d3d2-8ad2-4a53-aa65-ef42b26bbd33@posixcafe.org \
--to=moody@posixcafe.org \
--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).