From: Thorsten Glaser <tg@mirbsd.de>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
Richard Hartmann <richih.mailinglist@gmail.com>,
Git List <git@vger.kernel.org>
Subject: Re: Tracking file metadata in git -- fix metastore or enhance git?
Date: Fri, 8 Apr 2011 19:05:31 +0000 (UTC) [thread overview]
Message-ID: <Pine.BSM.4.64L.1104081903550.22999@herc.mirbsd.org> (raw)
In-Reply-To: <20110408185924.GA25840@elie>
Jonathan Nieder dixit:
>I think the most native-looking way to store metadata associated to
>paths is .gitattributes. It also has the nice feature of allowing a
>single attribute to apply to multiple files.
Eh, no. Think of extended attributes like, say, NTFS Resource Forks.
They’re just different “lines” into the “plane” a file can be, if
you excuse the metapher. (All parallel, of course.) They are just
another facet of each file.
bye,
//mirabilos
--
22:20⎜<asarch> The crazy that persists in his craziness becomes a master
22:21⎜<asarch> And the distance between the craziness and geniality is
only measured by the success 18:35⎜<asarch> "Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent
next prev parent reply other threads:[~2011-04-08 19:15 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 [this message]
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.1104081903550.22999@herc.mirbsd.org \
--to=tg@mirbsd.de \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--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).