From: "H. Peter Anvin" <hpa@zytor.com>
To: Adam Hunt <kinema@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: /etc in git?
Date: Wed, 18 Jan 2006 20:59:38 -0800 [thread overview]
Message-ID: <43CF1CBA.8030206@zytor.com> (raw)
In-Reply-To: <b476569a0601182040w581b72b7xbb99845da4085646@mail.gmail.com>
Adam Hunt wrote:
> Do you have any more details by chance? Does it work? Does it work
> well? How does one do it?
I've put my home directory dot files into git, and I'm assuming it's
going to be a similar issue for /etc. I've found git to be unusually
suitable for this, for the following reasons:
- git can deal with only managing a handful of files from a large
hierarchy, without an insane performance penalty.
- git only needs one repository directory at the root of the tree, not
in each subdirectory.
The biggest *problem* with git is that it doesn't handle files which
need to have their permissions maintained.
-hpa
next prev parent reply other threads:[~2006-01-19 5:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 3:43 /etc in git? Adam Hunt
2006-01-19 4:35 ` Junio C Hamano
2006-01-19 4:40 ` Adam Hunt
2006-01-19 4:59 ` H. Peter Anvin [this message]
2006-01-19 5:05 ` Junio C Hamano
2006-01-19 6:23 ` Ryan Anderson
2006-01-19 7:50 ` Junio C Hamano
2006-01-19 9:41 ` [PATCH] Support precise tracking of file modes Petr Baudis
2006-01-19 18:25 ` Junio C Hamano
2006-01-19 18:46 ` Petr Baudis
2006-01-20 15:27 ` Alex Riesen
2006-01-20 14:16 ` Peter Baumann
2006-01-20 13:50 ` /etc in git? Ryan Anderson
2006-01-20 17:55 ` Junio C Hamano
2006-01-19 16:54 ` Joel Becker
2006-01-19 22:22 ` Daniel Barkalow
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=43CF1CBA.8030206@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=kinema@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).