Submitter | Augie Fackler |
---|---|
Date | Aug. 19, 2016, 1:27 p.m. |
Message ID | <B0E35965-869F-4AB3-A561-5576A5FC6CBF@durin42.com> |
Download | mbox | patch |
Permalink | /patch/16360/ |
State | Changes Requested |
Headers | show |
Comments
>>> Is there documentation that needs to be updated to mention this is now possible? (might be already done in another change in this series, but I didn't see it) >> >> I'm honestly not sure where to tuck this doc-wise, given that it matters for all boolean flags everywhere. Sigh. I'm very open to ideas... > > Here's one idea. I don't know how clear it is though. Left side of the diff is what we have today, right side of the diff is what I'm proposing. I don't love it, but maybe it helps? > > Kind of ugly though. Sigh. > + -C --clean[=(true|false)] discard uncommitted changes (no backup) > + -c --check[=(true|false)] require clean working directory > + --mq[=(true|false)] operate on patch repository I'm opposed to this style of docs. We should add some punctuation to each option that will support --no-, tentatively, I'd suggest one of `^`, ''~', or '!'. And after the table include: Options marked with '^' can be turned off using --no-[optionname] as in --no-check.
Patch
--- /dev/fd/11 2016-08-19 09:26:16.000000000 -0400 +++ /dev/fd/12 2016-08-19 09:26:16.000000000 -0400 @@ -31,11 +31,11 @@ options: - -C --clean discard uncommitted changes (no backup) - -c --check require clean working directory - -d --date DATE tipmost revision matching date - -r --rev REV revision - -t --tool VALUE specify merge tool - --mq operate on patch repository + -C --clean[=(true|false)] discard uncommitted changes (no backup) + -c --check[=(true|false)] require clean working directory + -d --date DATE tipmost revision matching date + -r --rev REV revision + -t --tool VALUE specify merge tool + --mq[=(true|false)] operate on patch repository (some details hidden, use --verbose to show complete help)