From: Jerome de Vivie <jerome.de-vivie@wanadoo.fr>
To: Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdev@vger.kernel.org,
maritza@libertsurf.fr, rusty@rustcorp.com.au
Subject: Re: Yet another linux filesytem: with version control
Date: Tue, 24 Jul 2001 00:27:22 +0200 [thread overview]
Message-ID: <3B5CA4CA.46B53843@wanadoo.fr> (raw)
In-Reply-To: <3B5C91DA.3C8073AC@wanadoo.fr> <20010723141751.W6820@work.bitmover.com> <3B5C9E95.8BF61D7A@wanadoo.fr> <20010723151457.C14194@work.bitmover.com>
Larry McVoy a écrit :
>
> On Tue, Jul 24, 2001 at 12:00:53AM +0200, Jerome de Vivie wrote:
> > I absolutely don't know how much work it is. Will you work again on this
> > topic ?
>
> Err, I've got a young but healthy company that is already doing it. I'm
> happy to offer what advice I can to help you but I can't really commit
> substantial resources towards this. I make my living off of my company
> and that has to come first. That said, it's an interesting area and it's
> nice to see others take an interest, so I'll help a little...
Ok, thanks !
>
> > To work on a file, we just break and copy the link. But, i don't see how
> > to work with 2 versions of the same file with hard link.
>
> You don't want to do so. You save little by doing so. Please tell me you
> weren't going to version control at the block level, therein lies the path
> to insanity. Getting it right at the file boundary is hard enough.
Yes, it was block level version control but it feets our needs ( I have
scattered files across directories when there were no dependencies).
j.
--
Jerome de Vivie jerome . de - vivie @ wanadoo . fr
next prev parent reply other threads:[~2001-07-23 22:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 21:06 Yet another linux filesytem: with version control Jerome de Vivie
2001-07-23 21:17 ` Larry McVoy
2001-07-23 21:51 ` Rik van Riel
2001-07-23 22:19 ` Jerome de Vivie
2001-07-23 22:29 ` Rik van Riel
2001-07-23 23:05 ` Jerome de Vivie
2001-07-23 23:30 ` Rik van Riel
2001-07-24 13:30 ` Olivier Galibert
2001-07-24 16:42 ` Jerome de Vivie
2001-07-23 23:14 ` Larry McVoy
2001-07-24 23:57 ` Peter A. Castro
2001-07-23 22:00 ` Jerome de Vivie
2001-07-23 22:14 ` Larry McVoy
2001-07-23 22:27 ` Jerome de Vivie [this message]
2001-07-24 5:24 ` Albert D. Cahalan
2001-07-24 5:34 ` Larry McVoy
2001-07-24 6:06 ` Alexander Viro
2001-07-24 9:30 ` Padraig Brady
2001-07-24 19:07 ` Jan Harkes
2001-07-24 2:13 ` Keith Owens
2001-07-24 13:07 ` Andrew Pimlott
2001-07-24 17:14 ` Jerome de Vivie
2001-07-24 19:05 ` Andrew Pimlott
2001-07-24 23:14 ` Jerome de Vivie
2001-07-25 0:39 ` Andrew Pimlott
-- strict thread matches above, loose matches on Subject: below --
2001-07-23 22:50 Florin Iucha
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=3B5CA4CA.46B53843@wanadoo.fr \
--to=jerome.de-vivie@wanadoo.fr \
--cc=linux-fsdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=maritza@libertsurf.fr \
--cc=rusty@rustcorp.com.au \
/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