[Bug 4985] New: `hg log --removed` argument isn't explained well

[mercurial-bugs at selenic.com]

https://bz.mercurial-scm.org/show_bug.cgi?id=4985

            Bug ID: 4985
           Summary: `hg log --removed` argument isn't explained well
           Product: Mercurial
           Version: default branch
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: bug
          Priority: normal
         Component: Mercurial
          Assignee: bugzilla at selenic.com
          Reporter: gregory.szorc at gmail.com
                CC: mercurial-devel at selenic.com

https://hg.mozilla.org/releases/mozilla-beta/ has a number of changes like
https://hg.mozilla.org/releases/mozilla-beta/rev/306aa9bb7942 and
https://hg.mozilla.org/releases/mozilla-beta/rev/4a08db68940e. Basically
performing the same delta to the same file.

`hg log build/defines`
(https://hg.mozilla.org/releases/mozilla-beta/log/default/build/defines.sh)
omits many of these changes because by default `hg log <file>` is looking at
the filelog and looking at linkrevs to see which changesets changed the file.
Since these changesets didn't introduce a new filelog entry, they don't show
up.

`hg help log` does say:

    Note:
       for performance reasons, log FILE may omit duplicate changes made on
       branches and will not show removals or mode changes. To see all such
       changes, use the --removed switch.

Later on:

    --removed             include revisions where files were removed

First, we might want to supplement "--removed" with "--duplicates" or
"--find-harder" or something because "removed" isn't the only thing this flag
does.

Second, it would be nice if the short help said something about showing
duplicates, otherwise someone needs to read the full help to discover this
wonky behavior.

-- 
You are receiving this mail because:
You are on the CC list for the bug.