Changes between Initial Version and Version 4 of Ticket #326


Ignore:
Timestamp:
Jul 20, 2010, 10:27:42 AM (13 years ago)
Author:
Jari Häkkinen
Comment:

Replying to peter:

For the codons we work on the file name, but I suppose it is more flexible to match on the whole path as it allows pattern such as "*/test/README"

This would of course match all README files in a directory test. If you decide to set a pattern README I suppose it should match all files name README but in my view this is not obvious. Following your example the pattern should be */README but I am not sure that is wanted. One way to avoid it is to use test/README or ./test/README. I realize while writing this that we need to define from where the pattern matching starts. And it should be from the current directory, and then your example makes sense to me. We would have

`cwd`/*/test/README
`cwd`/README
`cwd`/*/README
`cwd`/test/README
`cwd`/./test/README

for the five examples discussed sofar. The current working directory of course changes as the directory tree is traversed. This means that the third example would not match a REAMDE in the search root directory (compare matching using ls). This leads to another thought, since ls does some nice pattern matching the functionality surely exists in a lib somewhere, maybe we can use it?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #326

    • Property Status changed from new to assigned
    • Property Milestone changed from svndigest 0.8 to svndigest 0.9
  • Ticket #326 – Description

    initial v4  
    33Motivation for this feature:
    44
    5   - It is more convenient to set a pattern e.g. `*.java` than setting the propert on each of these files. In principle one could use subversion's autoprops for this, but allowing this in svndigest also allow the user to set this afterwards. In [http://baseplugins.thep.lu.se baseplugins] for example they use a non-standard tree structure with tags and branches far out in the tree. This feature would allow a user to ignore all tags for example.
     5  - It is more convenient to set a pattern e.g. `*.java` than setting the property on each of these files. In principle one could use subversion's autoprops for this, but allowing this in svndigest also allow the user to set this afterwards. In [http://baseplugins.thep.lu.se baseplugins] for example they use a non-standard tree structure with tags and branches far out in the tree. This feature would allow a user to ignore all tags for example.
    66  - It allows a user to set ignore also when running on repository he does not have write permission on.
    77
     
    1111}}}
    1212that should be used in Node::ignore.
    13