From: Junio C Hamano <gitster@pobox.com>
To: Bob Bell <b_git@thebellsplace.com>
Cc: git@vger.kernel.org
Subject: Re: Using clean/smudge scripts from repository
Date: Wed, 10 Jun 2015 08:22:18 -0700 [thread overview]
Message-ID: <xmqq1thjoafp.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150610015349.GA5417@robin.thebellsplace.net> (Bob Bell's message of "Tue, 9 Jun 2015 21:53:50 -0400")
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.
next prev parent reply other threads:[~2015-06-10 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 1:53 Using clean/smudge scripts from repository Bob Bell
2015-06-10 15:22 ` Junio C Hamano [this message]
2015-06-10 20:55 ` Bob Bell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1thjoafp.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=b_git@thebellsplace.com \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).