git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Using clean/smudge scripts from repository

From
BBBob Bell <b_git@thebellsplace.com>
Date
Jun 10, 2015, 20:55 UTC
Message-ID
<20150610205542.GB5417@robin.thebellsplace.net>
In-Reply-To
<xmqq1thjoafp.fsf@gitster.dls.corp.google.com>
On Wed, Jun 10, 2015 at 08:22:18AM -0700, Junio C Hamano wrote:
Show 10 quoted lines
> Bob Bell <b_git@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

Previous: Junio C Hamano
Message 3 of 3 in “Using clean/smudge scripts from repository”
  1. Bob BellJun 10, 2015
  2. Junio C HamanoJun 10, 2015
  3. Bob BellJun 10, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.