[PATCH v3 1/8] clarify %f documentation
- From
Joey Hess <joeyh@joeyh.name>
- Date
- Jun 22, 2016, 20:21 UTC
- Message-ID
- <20160622202133.23565-2-joeyh@joeyh.name>
- In-Reply-To
- <20160622202133.23565-1-joeyh@joeyh.name>
It's natural to expect %f to be an actual file on disk; help avoid that mistake.
Signed-off-by: Joey Hess <joeyh@joeyh.name> --- Documentation/gitattributes.txt | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt index e3b1de8..145dd10 100644 --- a/Documentation/gitattributes.txt +++ b/Documentation/gitattributes.txt @@ -374,6 +374,11 @@ substitution. For example: smudge = git-p4-filter --smudge %f ------------------------ +Note that "%f" is the name of the path that is being worked on. Depending +on the version that is being filtered, the corresponding file on disk may +not exist, or may have different contents. So, smudge and clean commands +should not try to access the file on disk, but only act as filters on the +content provided to them on standard input. Interaction between checkin/checkout attributes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-- 2.9.0.8.g973eabb.dirty