git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Smith <yarcs@qualitycode.com>
To: git@vger.kernel.org
Subject: SCM ideas from 2003
Date: Mon, 18 Apr 2005 23:38:37 -0400	[thread overview]
Message-ID: <42647D3D.6030906@qualitycode.com> (raw)

I just stumbled across this page, dated 2003, which foreshadows a couple
of the decisions Linus has made for git:

  http://ydirson.free.fr/en/software/scm/vc.txt

Here are the parts that particularly caught my eye:

"what's so special about files ?" where the author suggests that
existing SCM systems are so blinded by the tradition of file orientation
that they can't see that there might be alternatives.

"As a goodie we can even note that moving a file inside the hierarchy
has become exactly similar as moving a code statement." where the author
recognizes that renames are merely a special case of code moves.

His implementation ideas are quite different from git, but I thought it
was pretty cool to find that someone was thinking about these ideas a
couple years ago.

Kevin

             reply	other threads:[~2005-04-19  3:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19  3:38 Kevin Smith [this message]
2005-04-19  5:31 ` SCM ideas from 2003 Marc Girod
2005-04-19  8:07   ` A VFS layer - was: " Jon Seymour
2005-04-19 23:13     ` Stéphane Fillod

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=42647D3D.6030906@qualitycode.com \
    --to=yarcs@qualitycode.com \
    --cc=git@vger.kernel.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).