From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: Preserving ownership and set*id bits
Date: Thu, 18 Jan 2007 20:10:39 +0000 [thread overview]
Message-ID: <200701182010.41183.andyparkins@gmail.com> (raw)
In-Reply-To: <769697AE3E25EF4FBC0763CD91AB1B0201D49679@MBGMail01.mobot.org>
On Thursday 2007, January 18 17:09, Ron Parker wrote:
> Anyway, I'm not here to complain, but I am looking for suggestions of
> how I might store and preserve this information as well.
Storing it is fairly easy. You can use getfacl in the pre-commit hook to
record all the file information you want.
The hard part (at the moment) is that there is no post-checkout hook that you
could use to restore those attributes.
If you were willing to manually run that restoration script after every
checkout then there is your answer.
Andy
--
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com
prev parent reply other threads:[~2007-01-18 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 17:09 Preserving ownership and set*id bits Ron Parker
2007-01-18 20:10 ` Andy Parkins [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=200701182010.41183.andyparkins@gmail.com \
--to=andyparkins@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).