From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Bakul Shah <bakul@bitblocks.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] SCCS
Date: Sat, 14 Sep 2019 01:12:21 +0200 [thread overview]
Message-ID: <20190913231221.-skm3%steffen@sdaoden.eu> (raw)
In-Reply-To: <20190913214905.339ED1570CE9@mail.bitblocks.com>
Bakul Shah wrote in <20190913214905.339ED1570CE9@mail.bitblocks.com>:
|On Fri, 13 Sep 2019 14:17:51 -0700 Larry McVoy <lm@mcvoy.com> wrote:
|> On Fri, Sep 13, 2019 at 11:11:04PM +0200, Steffen Nurpmeso wrote:
|>>
|>> I for one am so happy to have git that i cannot tell you how much
|>> that is. I have used rcs, cvs, subversion, back to cvs,
|>> mercurial over the years,, and for some small things also sccs.
|>> All of it has been a pain here or there. Yes, the weave. Schily
|>> wants to provide real changeset support for sccs (tagging is real
|>> problem), i think.
|>
|> I don't know why, BitKeeper does that and is open source under
|> a liberal license (Apache v2).
|
|This is because in git the "id" of a changeset is its sha1
|checksum. Given that, you can only reference it in a
|subsequent changeset. This is a problem in that there is no
|git built-in way to correlate a built binary with a particular
|changeset id of its sources but you end up using your own
|convention. E.g. set env. var VERSION or some such to the id
|during the compile step but it is a bother.
Linus Torvalds wrote an interesting message on that many years
ago, which someone pointed me at ditto. Do not ask. git cannot
generate human readable things by design, with branching and
merging, and due to the distributed nature. I have a little (git
pre-commit) script which keeps my SCCS IDs alive for my web pages,
even after i converted them to git. But i think for code bases
like NetBSD in particular this is a total show stopper (they
really keep the "original" file preamble alive, do they?), but it
also is for OpenBSD i think, and for FreeBSD i know that having
a human readible sequentially increasing version number was a main
reason to go for subversion. Even though there seems to be
a growing number of people who want to switch to git, yes i think
Warner Losh just said something like "when we will have switched
to git, that will xy", this week?
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
next prev parent reply other threads:[~2019-09-13 23:12 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 6:25 [TUHS] PWB vs Unix/TS Warner Losh
2019-09-09 6:36 ` arnold
2019-09-10 15:16 ` Clem Cole
2019-09-11 0:28 ` Steve Johnson
2019-09-11 3:53 ` Warner Losh
2019-09-11 15:36 ` Clem Cole
2019-09-11 16:55 ` [TUHS] IBM Unix source licenses [was " Charles H Sauer
2019-09-12 19:31 ` Kevin Bowling
2019-09-12 20:59 ` Clem Cole
2019-09-12 21:09 ` [TUHS] IBM Unix source licenses - Series/1 NUXI Ronald Natalie
2019-09-12 21:31 ` [TUHS] IBM Unix source licenses [was Re: PWB vs Unix/TS Warner Losh
2019-09-12 22:30 ` jcs
2019-09-12 23:12 ` reed
2019-09-12 23:22 ` jcs
2019-09-12 23:29 ` [TUHS] IBM Unix source licenses Warren Toomey
2019-09-13 7:06 ` arnold
2019-09-13 8:30 ` SPC
2019-09-14 18:29 ` Warner Losh
2019-09-12 21:29 ` [TUHS] IBM Unix source licenses [was Re: PWB vs Unix/TS Charles H Sauer
2019-09-11 17:49 ` [TUHS] " Richard Salz
2019-09-11 17:52 ` ron
2019-09-11 21:44 ` Clem Cole
2019-09-11 18:11 ` Larry McVoy
2019-09-11 18:18 ` Richard Salz
2019-09-11 18:54 ` Larry McVoy
2019-09-11 21:05 ` Steve Johnson
2019-09-11 21:34 ` Steve Johnson
2019-09-11 21:57 ` Clem Cole
2019-09-11 22:50 ` Arthur Krewat
2019-09-11 21:59 ` Clem Cole
2019-09-11 21:50 ` Clem Cole
2019-09-11 22:49 ` Dave Horsfall
2019-09-12 3:43 ` [TUHS] SCCS Larry McVoy
2019-09-12 4:20 ` George Michaelson
2019-09-12 4:31 ` [TUHS] [SPAM] SCCS Larry McVoy
2019-09-12 13:44 ` Tony Finch
2019-09-13 4:11 ` Larry McVoy
2019-09-13 5:54 ` Dave Horsfall
2019-09-13 8:00 ` Peter Jeremy
2019-09-13 15:23 ` Larry McVoy
2019-09-13 21:36 ` Dave Horsfall
2019-09-12 4:28 ` [TUHS] SCCS Jon Forrest
2019-09-12 4:33 ` Larry McVoy
2019-09-12 6:12 ` William Corcoran
2019-09-12 14:35 ` Clem Cole
2019-09-13 5:22 ` Dave Horsfall
2019-09-13 5:50 ` Bakul Shah
2019-09-12 16:45 ` Eric Allman
2019-09-12 17:29 ` Clem Cole
2019-09-12 17:47 ` Warner Losh
2019-09-13 8:12 ` emanuel stiebler
2019-09-13 21:11 ` Steffen Nurpmeso
2019-09-13 21:17 ` Larry McVoy
2019-09-13 21:48 ` Bakul Shah
2019-09-13 23:12 ` Steffen Nurpmeso [this message]
2019-09-13 23:03 ` Steffen Nurpmeso
2019-09-14 1:55 ` [TUHS] [SPAM] SCCS Larry McVoy
2019-09-16 17:23 ` [TUHS] SCCS Steffen Nurpmeso
2019-09-16 20:31 ` Larry McVoy
2019-09-17 17:57 ` Steffen Nurpmeso
2019-09-18 8:48 ` Eric Allman
2019-09-18 17:33 ` Steffen Nurpmeso
2019-09-12 20:07 ` Nemo
2019-09-11 16:05 ` [TUHS] PWB vs Unix/TS Paul Winalski
2019-09-11 17:14 ` ron
2019-09-14 0:44 ` [TUHS] a book (was Re: PWB vs Unix/TS) reed
2019-09-14 2:53 ` Warner Losh
2019-09-15 2:18 ` Jon Steinhart
2019-09-15 2:39 ` Clem Cole
2019-09-15 3:24 ` Adam Thornton
2019-09-14 22:46 ` Clem cole
2019-09-15 0:58 ` Adam Thornton
2019-09-15 3:30 ` Eric Allman
2019-09-15 4:21 ` Larry McVoy
2019-09-15 5:17 ` Jon Steinhart
2019-09-15 20:14 ` Clem Cole
2019-09-15 20:21 ` Jon Steinhart
2019-09-15 20:12 ` Clem Cole
2019-09-15 21:28 ` Dave Horsfall
2019-09-15 23:27 ` Clem cole
2019-09-15 23:45 ` Richard Salz
2019-09-15 7:43 ` Andy Kosela
2019-09-12 4:25 [TUHS] SCCS Jon Steinhart
2019-09-13 21:37 Norman Wilson
2019-09-13 21:51 ` Larry McVoy
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=20190913231221.-skm3%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=bakul@bitblocks.com \
--cc=tuhs@minnie.tuhs.org \
/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).