This revision was automatically updated to reflect the committed changes.
Closed by commit rHGb0262b25ab48: help: adding a topic on flags (authored by
rdamazio, committed by ).
CHANGED PRIOR TO COMMIT
https://phab.mercurial-scm.org/D1270?vs=3359=3445#toc
REPOSITORY
rHG Mercurial
CHANGES
yuja accepted this revision.
yuja added a comment.
This revision is now accepted and ready to land.
Removed -f=foo and queued, thanks.
> it makes permanent my --no- boolean prefix for flags,
Perhaps we can add some note saying --no- is still experimental?
INLINE COMMENTS
>
durin42 accepted this revision as: durin42.
durin42 added a comment.
I'm +1 on this, but won't accept as a reviewer since I've got at least two
biases here (it makes permanent my --no- boolean prefix for flags, and it'll
solve some support problems at G).
REPOSITORY
rHG Mercurial
rdamazio marked 4 inline comments as done.
rdamazio added inline comments.
INLINE COMMENTS
> martinvonz wrote in flags.txt:67
> Do we recommend overriding the command like this or should the left side be
> called something else (maybe "icommit")? I really don't know what we
> recommend here,
rdamazio updated this revision to Diff 3359.
rdamazio marked 4 inline comments as done.
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST UPDATE
https://phab.mercurial-scm.org/D1270?vs=3334=3359
REVISION DETAIL
https://phab.mercurial-scm.org/D1270
AFFECTED FILES
contrib/wix/help.wxs
martinvonz added inline comments.
INLINE COMMENTS
> flags.txt:8
> +Additionally, some flags, such as --repository, are global and can be used
> with
> +any command - those are seen in :hg:`help -v`, and can be specified.
> +
The final "and can be specified" sounds a little truncated. Was there
rdamazio updated this revision to Diff 3334.
rdamazio marked 4 inline comments as done.
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST UPDATE
https://phab.mercurial-scm.org/D1270?vs=3168=3334
REVISION DETAIL
https://phab.mercurial-scm.org/D1270
AFFECTED FILES
contrib/wix/help.wxs
rdamazio added a comment.
In https://phab.mercurial-scm.org/D1270#21058, @martinvonz wrote:
> We're in code freeze for approximately two more days, so this will have to
wait until ~Thursday. Still, thanks for the patch. I'm happy to include
something like this. Things that struck me as
av6 added inline comments.
INLINE COMMENTS
> flags.txt:7
> +Mercurial command-line flags can be strings, numbers, booleans, or lists of
> +strings.
> +
This "lists of strings" caught my attention, but it took me some time to figure
out what's the matter. I don't feel strongly, but here are
dlax added inline comments.
INLINE COMMENTS
> flags.txt:30
> +In order to set a default value for a flag in an hgrc file, set it under the
> +[defaults] section of the hgrc file::
> +
`hg help config` says that "defaults" are deprecated and that aliases should be
used instead.
REPOSITORY
martinvonz added a comment.
We're in code freeze for approximately two more days, so this will have to
wait until ~Thursday. Still, thanks for the patch. I'm happy to include
something like this. Things that struck me as missing:
1. Long vs short form (that e.g. "--verbose" and "-v" are
rdamazio created this revision.
Herald added a subscriber: mercurial-devel.
Herald added a reviewer: hg-reviewers.
REVISION SUMMARY
This is a short topic to explain how command-line flags can be specified.
Some users have been confused by hg offerring different flag syntax than some
12 matches
Mail list logo
