All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Richard Hartmann <richih.mailinglist@gmail.com>
Cc: Thorsten Glaser <tg@mirbsd.de>, Git List <git@vger.kernel.org>
Subject: Re: Tracking file metadata in git -- fix metastore or enhance git?
Date: Fri, 08 Apr 2011 12:01:14 +0200	[thread overview]
Message-ID: <4D9EDCEA.9010903@drmicha.warpmail.net> (raw)
In-Reply-To: <BANLkTink-c8JuxnMBCAmXiVwFkBxJrTucw@mail.gmail.com>

Richard Hartmann venit, vidit, dixit 08.04.2011 02:29:
> On Thu, Apr 7, 2011 at 21:27, Thorsten Glaser <tg@mirbsd.de> wrote:
> 
>> 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.
> 
> etckeeper does exist and it's very useful.

While I think there is some consensus not to have attribs (besides x) in
core git, contrib/ may be a good place.

Note that etckeeper and metastore predate our notes feature. By now, a
notes tree is a perfect place to store meta information. You can attach
notes to blobs perfectly (see textconv-cache). That may be an option for
a reimplementation, depending on how you want the versioning of the
files to be related with the versioning of the meta data.

Michael

  reply	other threads:[~2011-04-08 10:01 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
2011-04-08  0:29   ` Richard Hartmann
2011-04-08 10:01     ` Michael J Gruber [this message]
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

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

  git send-email \
    --in-reply-to=4D9EDCEA.9010903@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=richih.mailinglist@gmail.com \
    --cc=tg@mirbsd.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.