The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ronald Natalie)
Subject: [TUHS] Claim your early Unix contributions on GitHub
Date: Wed, 30 Mar 2016 16:06:50 -0400	[thread overview]
Message-ID: <7EFB9801-867A-47BD-824E-53FCB29518F7@ronnatalie.com> (raw)
In-Reply-To: <1459362519.18225.for-standards-violators@oclsc.org>


> On Mar 30, 2016, at 2:28 PM, Norman Wilson <norman at oclsc.org> wrote:
> 
> Marc Rochkind:
>  One thing that really bugged me was
> those systems' inherent belief that you rarely want to keep a
> checked-out copy of something except while you're working on it.
> Another, harder to work around, is that in any nontrivial project
> there are often stages when I want to make changes of scope broader
> than a single file: factor common stuff out into a new file, merge
> things into a single file, rename files, etc.

Yeah, I hear you.   We wrote wrappers for most of the RCS commands to do checkin and then checkout unlocked.   The EMACS macros were helpful in this because it assumed you worked the way you do (look at a read-only version when not checked out for editing).

We just jumped the version numbers when we needed a common point.

We lived with RCS until we switched to Clearcase.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2284 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160330/1cb6930b/attachment.bin>


  reply	other threads:[~2016-03-30 20:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 18:28 Norman Wilson
2016-03-30 20:06 ` Ronald Natalie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-30  7:53 Diomidis Spinellis
2016-03-30 12:31 ` Joerg Schilling
2016-03-30 13:10   ` Diomidis Spinellis
2016-03-30 13:44     ` Joerg Schilling
2016-03-30 19:17   ` Larry McVoy
2016-03-30 21:07     ` Random832
2016-03-30 23:03       ` Joerg Schilling
2016-03-31  3:20       ` Larry McVoy
2016-03-31  3:34         ` Random832
2016-03-31  3:40           ` Larry McVoy
2016-03-30 23:42     ` Joerg Schilling
2016-03-31  3:54       ` Larry McVoy
2016-03-30 14:25 ` Marc Rochkind
2016-03-30 15:23   ` Joerg Schilling
2016-03-30 19:14     ` Larry McVoy
2016-03-30 15:49   ` Diomidis Spinellis
2016-03-30 16:07     ` Joerg Schilling
2016-03-30 16:29       ` Diomidis Spinellis
2016-03-30 16:14     ` Pat Barron
2016-03-31 21:06       ` Clem Cole
2016-03-31 21:54         ` Ron Natalie
2016-04-01  9:01         ` Diomidis Spinellis
2016-04-01 14:41           ` Clem Cole
2016-04-01 21:00           ` Jeremy C. Reed
2016-04-01 13:06         ` Dave Horsfall
2016-04-01 21:52         ` Pat Barron
2016-03-30 16:30     ` Marc Rochkind
2016-03-30 16:40       ` Joerg Schilling
2016-03-30 16:55       ` John Cowan

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=7EFB9801-867A-47BD-824E-53FCB29518F7@ronnatalie.com \
    --to=ron@ronnatalie.com \
    /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).