From: Miguel Ramos <mail@miguel.ramos.name>
To: david@lang.hm
Cc: Gabriel Filion <lelutin@gmail.com>, git@vger.kernel.org
Subject: Re: Using a git repository on the root directory
Date: Sat, 17 Apr 2010 12:58:45 +0100 [thread overview]
Message-ID: <v2l3e2876431004170458ib2d40b28he1fb56906f94a7ed@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1004170439170.16996@asgard.lang.hm>
2010/4/17 <david@lang.hm>:
> On Sat, 17 Apr 2010, Miguel Ramos wrote:
>
>> Well, David, you certainly made a good case defending using a VCS for
>> filesystems.
>> However, a versioned filesystem should be more adequate for that.
>
> a versioned filesystem will not let you easily clone or backup your system.
> a versioned filesystem could be a nice UI to access a DVCS that would give
> you this sort of ability
>
>> Why would one want diffs, patches, branches, merges for the entire
>> filesystem?
>
> these all seem like very useful things to me
>
> diffs to find out what changed when a system gets broken, or after something
> new is installed.
>
> patches could be a way to either install software, or to propogate updates
> between systems.
>
> branches could easily be different systems
>
> merges are for when you have two systems each doing one job and you want to
> combine them onto one piece of hardware (could could do it with
> virtualization, if you are willing to pay the overhead). you wouldn't want
> to merge the binary files, but you would want to merge the branches that
> contain binary files.
>
> there are many reasons why you don't just use your linux distro tools to
> manage large numbers of machines and configurations.
>
> David Lang
Yes, you certainly are right.
It does open up a set of new possibilities.
Even better if it was based on a binary diff, because otherwise you
either had to be very conservative updating software or run out of
space.
--
Miguel Ramos <mail@miguel.ramos.name>
PGP A006A14C
next prev parent reply other threads:[~2010-04-17 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 20:44 Using a git repository on the root directory Miguel Ramos
2010-04-17 4:17 ` Gabriel Filion
2010-04-17 4:45 ` david
2010-04-17 11:15 ` Miguel Ramos
2010-04-17 11:48 ` david
2010-04-17 11:58 ` Miguel Ramos [this message]
2010-04-17 12:55 ` david
2010-04-17 8:42 ` Jakub Narebski
2010-04-17 11:39 ` Miguel Ramos
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=v2l3e2876431004170458ib2d40b28he1fb56906f94a7ed@mail.gmail.com \
--to=mail@miguel.ramos.name \
--cc=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=lelutin@gmail.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).