>Near the start of this thread we mentioned the main use cases. There >are basically two: > >* Confirm that the repository is in a good state (e.g. before/after a >backup); > >* Diagnostic mode for use when a problem has been encountered. > >Keep-going mode is more useful for the latter; stop-quickly mode *may* >be more useful (and is certainly fine) for the former. So it's not >obvious that changing the default mode is a good idea. > Yes, I don't want to change the default behaviour either. Because if the --keep-going behaviour is made default, we would need a quick-stop mode to just see if the repo is sane, which a normal user would want to be the default behaviour of svnadmin verify. -- Prabhu
- Re: [PATCH] Implement svnadmin verify --force Stefan Sperling
- Re: [PATCH] Implement svnadmin verify --force Julian Foad
- Re: [PATCH] Implement svnadmin verify --force Prabhu Gnana Sundar
- Re: [PATCH] Implement svnadmin verify --force Julian Foad
- Re: [PATCH] Implement svnadmin verify --force Prabhu Gnana Sundar
- Re: [PATCH] Implement svnadmin verify --force Daniel Shahaf
- RE: [PATCH] Implement svnadmin verify --force Bert Huijben
- Re: [PATCH] Implement svnadmin verify --force Stefan Sperling
- Re: [PATCH] Implement svnadmin verify --force Mark Phippard
- Re: [PATCH] Implement svnadmin verify --force Julian Foad
- Re: [PATCH] Implement svnadmin verify --force Prabhu Gnana Sundar
- Re: [PATCH] Implement svnadmin verify --force Prabhu Gnana Sundar
- Re: [PATCH] Implement svnadmin verify --force Daniel Shahaf
- Re: [PATCH] Implement svnadmin verify --force Daniel Shahaf
- Re: [PATCH] Implement svnadmin verify --force Prabhu Gnana Sundar
- Re: [PATCH] Implement svnadmin verify --force Stefan Sperling
- Re: [PATCH] Implement svnadmin verify --force Daniel Shahaf
- Re: [PATCH] Implement svnadmin verify --force Julian Foad
- Re: [PATCH] Implement svnadmin verify --force Prabhu Gnana Sundar
- Re: [PATCH] Implement svnadmin verify --force Daniel Shahaf
- Re: [PATCH] Implement svnadmin verify --force Stefan Sperling