Re: [PATCH 1/4] clarify %f documentation

Joey Hess writes: > Junio C Hamano wrote: >> "tracked by Git" is not all that interesting, compared to the fact >> that your filter needs to give contents relevant to that path >> because that is what the command line argument Git gives you with >> '%f' means. It is not a

Re: [PATCH 1/4] clarify %f documentation

Junio C Hamano wrote: > "tracked by Git" is not all that interesting, compared to the fact > that your filter needs to give contents relevant to that path > because that is what the command line argument Git gives you with > '%f' means. It is not a random filename "tracked by Git". Among 47 >

Re: [PATCH 1/4] clarify %f documentation

Joey Hess writes: > Junio C Hamano wrote: >> I agree that "the name of the file" can be interpreted in many ways, >> and I agree that it would be a good idea to find a better phrase to >> name the path that is being worked on, but I do not think "the file >> in the git

Re: [PATCH 1/4] clarify %f documentation

Junio C Hamano wrote: > I agree that "the name of the file" can be interpreted in many ways, > and I agree that it would be a good idea to find a better phrase to > name the path that is being worked on, but I do not think "the file > in the git repository" is that phrase. > I think using the

Re: [PATCH 1/4] clarify %f documentation

Joey Hess writes: > It's natural to expect %f to be an actual file on disk; help avoid that > mistake. I agree that "the name of the file" can be interpreted in many ways, and I agree that it would be a good idea to find a better phrase to name the path that is being worked

[PATCH 1/4] clarify %f documentation

It's natural to expect %f to be an actual file on disk; help avoid that mistake. Signed-off-by: Joey Hess --- Documentation/gitattributes.txt | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/Documentation/gitattributes.txt