From: Richard Hartmann <richih.mailinglist@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Chris Webb <chris@arachsys.com>, Thorsten Glaser <tg@mirbsd.de>,
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: Sun, 10 Apr 2011 03:31:13 +0200 [thread overview]
Message-ID: <BANLkTimbAmW+ueq1Z9PJN9opXggywdxdnA@mail.gmail.com> (raw)
In-Reply-To: <7v39lqzzn9.fsf@alter.siamese.dyndns.org>
On Sun, Apr 10, 2011 at 03:03, Junio C Hamano <gitster@pobox.com> wrote:
> That is exactly why git does not store metainfo. Storing auxiliary
> information on commit objects or tree objects to help build or deploy
> procedures is fine, but that kind of information should be stored
> somewhere that the normal git operations would not care about.
Keeping this information out of git's way during operations in which
it's not needed is obviously A Good Thing. Yet, this would only happen
when this information has been added to the repository on purpose.
Thus, I don't see this as a deal-breaker.
Richard
next prev parent reply other threads:[~2011-04-10 1:31 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
2011-04-10 0:15 ` Jonathan Nieder
2011-04-10 1:03 ` Junio C Hamano
2011-04-10 1:31 ` Richard Hartmann [this message]
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=BANLkTimbAmW+ueq1Z9PJN9opXggywdxdnA@mail.gmail.com \
--to=richih.mailinglist@gmail.com \
--cc=chris@arachsys.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).