git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Thorsten Glaser <tg@mirbsd.de>
To: Richard Hartmann <richih.mailinglist@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Tracking file metadata in git -- fix metastore or enhance git?
Date: Thu, 7 Apr 2011 19:27:57 +0000 (UTC)	[thread overview]
Message-ID: <Pine.BSM.4.64L.1104071923580.4692@herc.mirbsd.org> (raw)
In-Reply-To: <BANLkTikkb3DUOtP9NUtNMNV5Z+oJ7AFHfg@mail.gmail.com>

Richard Hartmann dixit:

>git natively. metastore exists, but its binary storage format is

According to the documentation, metastore supports saving/restoring
POSIX Extended Attributes (however I got EOPNOTSUPP trying to setfacl
and setxattr, so I couldn’t verify the claim). It does *not* however
track the stuff visible using lsattr(1) on ext2fs.

Personally, I think this should definitively be tracked in git, not
in extra files (like “ EA DATA. SF” in OS/2) managed with external
tools (reminds me too much of things like umsdos and Rock Ridge as
well). Support needs not be part of core git, especially restoring
can be dangerous (consider SELinux), plus it’s very platform and
filesystem dependent, but seeing that people seem to want to use
git for keeping their /etc (I use RCS, myself, but volunteered my
C skill to change metastore if it needs be) there is definitively
a market for having it there, in a standardised manner.

bye,
//mirabilos
-- 
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh

  reply	other threads:[~2011-04-07 19:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07 19:16 Tracking file metadata in git -- fix metastore or enhance git? Richard Hartmann
2011-04-07 19:27 ` Thorsten Glaser [this message]
2011-04-08  0:29   ` Richard Hartmann
2011-04-08 10:01     ` Michael J Gruber
2011-04-08 18:59       ` Jonathan Nieder
2011-04-08 19:05         ` Thorsten Glaser
2011-04-08 19:45           ` Jonathan Nieder
2011-04-08 19:58             ` Thorsten Glaser
2011-04-08 21:23               ` Richard Hartmann
2011-04-09  8:11                 ` Chris Webb
2011-04-09  9:09                   ` Richard Hartmann
2011-04-10  0:15                     ` Jonathan Nieder
2011-04-10  1:03                       ` Junio C Hamano
2011-04-10  1:31                         ` Richard Hartmann
2011-04-11  0:12                           ` Richard Hartmann
2011-04-18  0:21 ` Richard Hartmann
2011-04-18  0:45   ` Jonathan Nieder
2011-12-14  4:54     ` johnnyutahh
2011-12-20  0:55       ` Richard Hartmann

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.BSM.4.64L.1104071923580.4692@herc.mirbsd.org \
    --to=tg@mirbsd.de \
    --cc=git@vger.kernel.org \
    --cc=richih.mailinglist@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).