git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kelvie Wong" <kelvie@ieee.org>
To: iiijjjiii <iiijjjiii@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Sharing home and etc files with git
Date: Thu, 5 Jun 2008 15:48:17 -0700	[thread overview]
Message-ID: <94ccbe710806051548x485aefe8j2ad6b40b74d68747@mail.gmail.com> (raw)
In-Reply-To: <48484607.5090505@gmail.com>

On 6/5/08, iiijjjiii <iiijjjiii@gmail.com> wrote:
> I would like to use git to keep revision histories of my home and etc
> directories. I have several computers and I like to keep their environments
> similar. I could see git pulls updating .bash_aliases, .bashrc, and various
> bash and perl scripts I create in the home directory, and updating /etc
> config files. Git pushes would share any recent changes to other computers.
> This way no matter which computer I am working on, the environment will be
> similar and I can make changes and know they will be copied to the others.
>

Completely understandable; also remember that pushing, unlike pulling, does not
update the working tree (and you wouldn't want it to).

>  I haven't figured out a good way to deal with the files that have local
> settings in them. Using .gitignore feels a little overkill. Only certain
> lines of the files need to be unique. Once they are set, I'd like subsequent
> changes to be updated. I could cherry-pick manually but I'd like a more
> automated method. I have read about etckeeper, git-home-history and gibak,
> but they seem to be designed for backing up and versioning files on one
> computer and not for sharing files.
>
>  Has anyone done something similar using git or is another tool more
> suitable.
>

I'm fairly certain there are tools out there for this, but what I do is I have
all of the files that I want to add (such as ~/.${SHELL}rc, ~/.${SHELL}.d/*,
and .emacs) into ~/.git-home; then I symlink all of these files/directories
into my $HOME (with a short script that's also checked in).

I then throw this entire repo somewhere where all my other machines can
pull/push from, and I resolve merges as needed.  It works fairly well.

-- 
Kelvie Wong

      parent reply	other threads:[~2008-06-05 22:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 20:01 Sharing home and etc files with git iiijjjiii
2008-06-05 20:50 ` Miklos Vajna
2008-06-05 22:48 ` Kelvie Wong [this message]

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=94ccbe710806051548x485aefe8j2ad6b40b74d68747@mail.gmail.com \
    --to=kelvie@ieee.org \
    --cc=git@vger.kernel.org \
    --cc=iiijjjiii@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).