git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Richard Hartmann <richih.mailinglist@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Thorsten Glaser <tg@mirbsd.de>, Harley J Pig <harleypig@gmail.com>
Subject: Re: Tracking file metadata in git -- fix metastore or enhance git?
Date: Mon, 18 Apr 2011 02:21:32 +0200	[thread overview]
Message-ID: <BANLkTimTszUC+4d3tMTP-cxG3AoWmr08HA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikkb3DUOtP9NUtNMNV5Z+oJ7AFHfg@mail.gmail.com>

Hi all,

as I don't want to let this go stale, here are the three options:

1) fix metastore
2) default to gitperms
3) extend git


I still think 3) would be best, but someone would need to step up to
do this. Is anyone up for this task? If not, we will have to resort to
1) or 2)


Thanks again,
Richard

  parent reply	other threads:[~2011-04-18  0:22 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
2011-04-11  0:12                           ` Richard Hartmann
2011-04-18  0:21 ` Richard Hartmann [this message]
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=BANLkTimTszUC+4d3tMTP-cxG3AoWmr08HA@mail.gmail.com \
    --to=richih.mailinglist@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=harleypig@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).