quoted
quoted
quoted
quoted
"Andy" == Andy Parkins [off-list ref] writes:
Andy> I've not done any extensive tests for regressions, but I've done
Andy> cd $HOME
Andy> git init
Andy> git add .bashrc
Andy> git add somedirectory/
Andy> And they work fine. So - it's works for me from me, and a big happy
Andy> grin.
Given that git currently doesn't maintain any metadata other than +x/-x, how
are you maintaining the metadata for your homedir items? I know some schemes
were discussed here in the past, but I'm curious as to what you settled on.
For example, your .netrc file needs to be 600, but git won't track that.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
[off-list ref] <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
On Saturday 2007, March 31, Randal L. Schwartz wrote:
Given that git currently doesn't maintain any metadata other than
+x/-x, how are you maintaining the metadata for your homedir items?
I know some schemes were discussed here in the past, but I'm curious
as to what you settled on. For example, your .netrc file needs to be
600, but git won't track that.
I'm not maintaining anything as yet; the experiment so far consists
of .bashrc only :-)
Just storing my .inputrc, .bashrc, .vimrc and .gitconfig in a repository
is probably going to give me all that I want. There aren't many other
config files that I regularly update, and certainly not many that I
update differently on different machines.
However, I plan to use a script to wrap the git calls so that I don't
have to type GIT_WORK_DIR and GIT_DIR for every file I want to track.
I plan to make it so that if you run this script with a checkout or
other working tree changing command then I will run a function within
it that reads the metadata out of a file that is stored in the
repository which will restore those settings.
Ideally this functionality would be in hooks for pre-update-index and
post-checkout-index or similar. But I have a feeling that the
potential for conflicts makes it hard to do in reality.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
On Sat, Mar 31, 2007 at 07:54:37AM -0700, Randal L. Schwartz wrote:
Given that git currently doesn't maintain any metadata other than +x/-x, how
are you maintaining the metadata for your homedir items? I know some
schemes
were discussed here in the past, but I'm curious as to what you settled on.
For example, your .netrc file needs to be 600, but git won't track that.
I personally just don't track files that have sensitive data. I tend to have
copies of my home dir on somewhat public servers, so I don't want that data
copied around anyway.
Tom