On Wed, Jun 10, 2015 at 08:22:18AM -0700, Junio C Hamano wrote:
Bob Bell b_...@thebellsplace.com writes:
Is this a proper solution, or did I just luck out? Am I perhaps
doing something foolish?
Yes, we happen to run checkout in the index order, but that is not
something we guarantee, so you can call yourself lucky. You are
being doubly lucky that nobody in your project is committing a
malicious script in the repository. It may also count as foolish,
depending on how important the security is for you and how
trustworthy your collaborators are.
Hrm, that's unfortunate. So I gather it'll work, consistently, but
there's no guarantee that future versions of git won't break the
ordering assumption? Is there anything available I can leverage here?
git has to at least assure that .gitattributes is checked out before the
files to which it could refer, right?
This is development in a corporate environment, and the collaborators
are trustworthy. The alternative is to place the files on some network
share, where the same collaborators could edit it, etc. But I was
hoping for a more self-contained solution, without such dependencies.
Thanks,
Bob
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
