> Subject: [PATCH 1/3] Add support for new %w wildcard in checkout filter Please write your title to help readers of "git shortlog --no-merges". With the above, readers would not know where the %w would newly be allowed to appear, what it does, and how it helps what use case. > When building content filters with gitattributes, for instance to ensure > git stores the plain-text rather than the binary form of data for certain > formats, it is often advantageous to separate the filters into separate, > potentially complex scripts. However, as the $PWD where content filters > are executed is unspecified the path to scripts needs to be specified as > an absolute path. Isn't $PWD at least stable in a repository, relative to the top of worktree or something? IOW, isn't the above raise a separate documentation issue that is better solved without any new code? > That means that the guide for setting up a repository > which uses scripts to filter content cannot simply consist of "include > the following lines in your .git/config file", and it means that the > otherwise safe operation of moving a git repository from one folder to > another is decidedly unsafe. If these paths are given as absolute paths (e.g. ~/filter-scripts/), the repositories that refer to these can be moved freely, as long as the location of the the directory that holds these auxiliary scripts is kept stable, no?
