public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Mielke <mark@mark.mielke.cc>
To: Stevie O <stevie@qrpff.net>
Cc: Larry McVoy <lm@bitmover.com>, Kent Borg <kentborg@borg.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Versioning File Systems?
Date: Fri, 19 Apr 2002 00:12:08 -0400	[thread overview]
Message-ID: <20020419001208.A14615@mark.mielke.cc> (raw)
In-Reply-To: <20020418110558.A16135@borg.org> <20020418110558.A16135@borg.org> <20020418082025.N2710@work.bitmover.com> <5.1.0.14.2.20020418191904.028f1290@whisper.qrpff.net>

On Thu, Apr 18, 2002 at 07:19:47PM -0400, Stevie O wrote:
> At 08:20 AM 4/18/2002 -0700, Larry McVoy wrote:
> >It's certainly a fun space, file system hacking is always fun.  There
> >doesn't seem to be a good match between file system operations and
> >SCM operations, especially stuff like checkin.  write != checkin.
> >But you can handle that with
> How about
>         fsync(fd) || close(fd) == checkin?

Source management systems usually work much better given explicit
control for the user.

ClearCase has MVFS to do what is being suggested. Compare:

    cat a.c                 # currently selected version of a.c
    cat a.c@@/main/5        # version 5 on the main branch

    cat a.c@@LINUX_2.4.18   # the version of a.c selected by the
                            # label 'LINUX_2.4.18'

Having a file system that implicitly performs these operations is
not very useful.

mark

-- 
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
.  .  _  ._  . .   .__    .  . ._. .__ .   . . .__  | Neighbourhood Coder
|\/| |_| |_| |/    |_     |\/|  |  |_  |   |/  |_   | 
|  | | | | \ | \   |__ .  |  | .|. |__ |__ | \ |__  | Ottawa, Ontario, Canada

  One ring to rule them all, one ring to find them, one ring to bring them all
                       and in the darkness bind them...

                           http://mark.mielke.cc/


  reply	other threads:[~2002-04-19  4:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18 15:05 Versioning File Systems? Kent Borg
2002-04-18 15:20 ` Larry McVoy
2002-04-18 15:27   ` Lars Marowsky-Bree
2002-04-18 16:55     ` Kent Borg
2002-04-18 17:04       ` Joshua MacDonald
2002-04-20  8:44       ` Thomas Zimmerman
2002-04-18 23:19   ` Stevie O
2002-04-19  4:12     ` Mark Mielke [this message]
2002-04-18 18:11 ` Jeremy Jackson
2002-04-23 22:42 ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2002-04-18 16:51 Kerl, John
2002-04-18 17:24 ` Florin Iucha
2002-04-18 18:14   ` Kent Borg

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=20020419001208.A14615@mark.mielke.cc \
    --to=mark@mark.mielke.cc \
    --cc=kentborg@borg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=stevie@qrpff.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