git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pierre-Julien Bringer" <pj.bringer@gmail.com>
To: git@vger.kernel.org
Subject: keeping /etc under git with etckeeper
Date: Sat, 9 Aug 2008 20:48:39 +0200	[thread overview]
Message-ID: <14b409fc0808091148k69f4019n6996261a710adfca@mail.gmail.com> (raw)

Do you think storing the etc directory in git with etckeeper is a good
thing? I've heard it was not recommended to do so for the home
directory, but also for /etc:
1 Git tries to find a link between the changes and there would
probably be none for $HOME, according to Randal Schwarz [1].
2 Git does not store permissions of files [2].
3 If Git has some sort of merge conflict on important config files
(passwd, etc...), it would be pretty bad [3].

When using etckeeper:
1 There would be a link between the changes if a commit occurs between tasks.
2 Permissions are stored thanks to Metastore.

I have only superficial experience in using git, and I don't really
know how likely it would be for things to go wrong. Merging seems to
be the dangerous operation, but using it to track linear history would
be okay. Gentoo users have been able to use RCS for a long time, but
that solution is considered to be deprecated, although it does the
job. Can experienced git users think of any reason not to use a small
subset of git for this task?


Pierre-Julien Bringer


[1] Randal Schwarz, "Git" at Google, October 12 2007, available at
http://www.youtube.com/watch?v=8dhZ9BXQgc4
[2] Git project's FAQ available at http://git.or.cz/gitwiki/GitFaq
[3] Joey Hess, November 26 2007 on vcs-home -- Discussion list for
storing ~ under VCS control, available at
http://lists.madduck.net/pipermail/vcs-home/2007-November/000102.html

             reply	other threads:[~2008-08-09 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-09 18:48 Pierre-Julien Bringer [this message]
2008-08-09 19:16 ` keeping /etc under git with etckeeper martin f krafft
2008-08-09 23:42 ` Miklos Vajna
2008-08-10  3:15 ` Edward Z. Yang

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=14b409fc0808091148k69f4019n6996261a710adfca@mail.gmail.com \
    --to=pj.bringer@gmail.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).