Opened 12 years ago

Closed 11 years ago

#79 closed task (wontfix)

behaviour of --force

Reported by: peter Owned by: jari
Priority: trivial Milestone: svndigest 0.7
Component: core Version: trunk
Keywords: Cc:

Description (last modified by peter)

In context of #5 the --force option must be reinterpreted. The whole idea with #5 is to write the output in the same directory over and over again. How does --force fit in here?

Change History (5)

comment:1 Changed 12 years ago by peter

  • Description modified (diff)

comment:2 Changed 12 years ago by peter

This a sugestion for new interpretation of --force flag.

Running something like svndigest --root root --target target.

  1. If there is a file named root in target --> burp
  2. If there is no directory named root in target --> proceed
  3. If there is a directory named root in target and that directory has sub-directory called .svndigest --> proceed and if --force is set ignore last parsing else use the saved Stats in .svndigest directories.
  4. If there is a directory named root in target but that directory has no sub-directory named .svndigest --> burp unless --force is set.

comment:3 Changed 12 years ago by jari

  • Status changed from new to assigned

comment:4 Changed 11 years ago by jari

  • Status changed from assigned to new

comment:5 Changed 11 years ago by jari

  • Resolution set to wontfix
  • Status changed from new to closed

The chache will reside in the source directory so there is no need to redefine --force.

Note: See TracTickets for help on using tickets.