From: Richard Hartmann <richih.mailinglist@gmail.com>
To: Chris Webb <chris@arachsys.com>
Cc: Thorsten Glaser <tg@mirbsd.de>,
Jonathan Nieder <jrnieder@gmail.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
Git List <git@vger.kernel.org>
Subject: Re: Tracking file metadata in git -- fix metastore or enhance git?
Date: Sat, 9 Apr 2011 11:09:22 +0200 [thread overview]
Message-ID: <BANLkTim5DPjGjJ=SfnNfXpzCd6=PKnSs6g@mail.gmail.com> (raw)
In-Reply-To: <20110409081108.GE13750@arachsys.com>
On Sat, Apr 9, 2011 at 10:11, Chris Webb <chris@arachsys.com> wrote:
> (Disclaimer: I've never tried using smudge filters; maybe they can't be used
> in the way I describe!)
Smudge filters are on my half-read list of New Cool Stuff so I can't
really comment on this.
Another idea would be to simply tack all metadata into the same place
as the existing chmod stuff.
While one large text file would be nice in case one wanted to make
manual changes, attaching versioned, binary information to every
object directly is a lot more efficient. I think I am convinced the
latter would be the cleaner approach, now. With a clean layout, this
would not need to be a huge code drop supporting every metadata type
in existence; it could be extended as needed.
As noted above, .gitattributes could be used to manage what kind of
metadata should be stored.
One large question in my mind is if anyone who's familiar enough with
the codebase and has the time would be interested in actually
implementing this.
Thanks,
Richard
next prev parent reply other threads:[~2011-04-09 9:10 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
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 [this message]
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='BANLkTim5DPjGjJ=SfnNfXpzCd6=PKnSs6g@mail.gmail.com' \
--to=richih.mailinglist@gmail.com \
--cc=chris@arachsys.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jrnieder@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 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).