git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: "Randal L. Schwartz" <merlyn@stonehenge.com>
Subject: Re: git-add has gone lstat() mad
Date: Sat, 31 Mar 2007 16:09:21 +0100	[thread overview]
Message-ID: <200703311609.23309.andyparkins@gmail.com> (raw)
In-Reply-To: <86lkhdqx8y.fsf@blue.stonehenge.com>

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

  reply	other threads:[~2007-03-31 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30 19:55 git-add has gone lstat() mad Andy Parkins
2007-03-30 20:20 ` Andy Parkins
2007-03-31  1:38   ` Junio C Hamano
2007-03-31  3:39     ` Linus Torvalds
2007-03-31 10:18       ` Andy Parkins
2007-03-31 14:54         ` Randal L. Schwartz
2007-03-31 15:09           ` Andy Parkins [this message]
2007-03-31 19:28           ` Tom Prince
2007-04-01  0:39       ` Junio C Hamano
2007-04-01  8:25         ` Andy Parkins

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=200703311609.23309.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.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).