-
Notifications
You must be signed in to change notification settings - Fork 99
document required flags #159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
better :-) i still like the idea though, to provide an example rules-file if one is missing (the rules-file is not exactly something you encounter regularly, and having to search the accompanying examples for is tedious :-)) |
…utput-synopsis Improve synopsis line in usage output (fixes #159)
@umlaeute cool, thanks for the review!
I see pros and cons with this idea and consider it a separate issue. I'll consider it more but tending towards not adding it. |
It's been a while since i used
svn-all-fast-export
, so I was slightly annoyed, that it doesn't work out-of-the-box as advertised in the help.The help says:
The way I read this, I have to (obviously) provide a
Path to subversion repo
, and that's about it.However, when trying to run as such, I get an error:
What's this
'rules' argument
? the help speaks of options rather than arguments (and options have leading dashes). I guess this is some leftover from a previous invocation style alasvn-all-fast-export /path/to/svnrepo /path/to/rules
.Also, the help mentions "rules file(s)", but it might be nice to provide an example of such a rules file (without having to go and find the
samples
directory first (esp. when using a distro-packaged version ofsvn-all-fast-export
)E.g. I would imagine something like this:
and
The text was updated successfully, but these errors were encountered: