[PATCH 1 of 1] churn: improve description

[timeless]

On Wed, Jun 17, 2009 at 12:15 PM, Cedric Duval<cedricduval at free.fr>
> While we are at it, a look at the whole extensions list might be in order.

yeah, just don't miss the deadline :)

in general, I like your changes.

>     "allow or deny access to parts of a repository"?

parts => portions ?
allow or deny => control ?

>  bookmarks       Mercurial bookmarks
>
>     "track a line of development with moving pointers"?

I don't like 'pointers' but can't offer something better

>  bugzilla        Bugzilla integration
>
>     "integrate Mercurial with the Bugzilla bug tracker"?

the => a

>  children        (no help text available)
>
>     "show the children of a revision"?
>
>  churn           command to show certain statistics about revision history
>
>     "display statistics about the repository history"?

drop "the"

>  convert         converting foreign VCS repositories to Mercurial
>
>     s/converting/convert/ ?

to => into ?
convert => import from ?

>  extdiff
>
>     "use an external diff tool"?
>
>  fetch           pulling, updating and merging in one command
>
>     "pull, update and merge in one command"?
>
>  gpg             (no help text available)
>
>     "sign and verify changesets"?
>
>  graphlog        show revision graphs in terminal windows
>
>     Ok

terminal windows => terminals ?

>  hgcia           CIA notification
>
>     "integrate Mercurial with the CIA notification service"?

the => a ? (is there *ONLY* one CIA in the whole world, or is it
something for which many people can run their own instances?)
>
>  hgk             browsing the repository in a graphical way
>
>     s/browsing/browse/ ?
>
>  highlight       syntax highlighting in hgweb, based on Pygments
>
>     Simply "hilight syntax in hgweb"? Leaving information about
>     dependencies to the longer description.

syntax highlighting for hgweb (and check the capitalization of 'hgweb')

>  inotify         inotify-based status acceleration for Linux systems
>
>     Probably ok, though perhaps we could leave out "inotify-based",
>     as it is obvious from the name of the extension, and the long
>     description is a better place to delve with technical details.

I'm pretty sure 'Linux' is wrong (at least Solaris, probably OS X,
maybe Windows?)

>  interhg         (no help text available)

>     "use the InterWiki syntax in changelog and summaries"?

use or support ? is this an input or output thing?

>  keyword         keyword expansion in local repositories
>
>     "expand keywords in the working directory"?
>
>     From the extension's description ("Keywords are only expanded in
>     local repositories and not stored in the change history."), the
>     above might be more accurate.

i think it's closer but problematic. I think you want "for" instead of
"in" somewhere, but I can't help beyond that.

>  mq              patch management and development
>
>     "work with a stack of patches"?
>
>     "... on top of the working directory"?

yes

>  notify          hook extension to email notifications on commits/pushes
>
>     "email notifications upon commits/pushes"?

upon => for

>  pager           browse command output with external pager

with => using an ?

>  parentrevspec   use suffixes to refer to ancestor revisions

use => support ?

>  patchbomb       sending Mercurial changesets as a series of patch emails
>
>     s/sending/send/ ?
>
>  purge           (no help text available)
>
>     "clean working directory from files not tracked by Mercurial"?

clear files that aren't tracked by Mercurial from the working directory

(good luck shortening it, but please be careful)

>  rebase          move sets of revisions to a different ancestor

i know what this does but really don't like 'ancestor' here.

>  record          interactive change selection during commit or qrefresh
>
>     "interactively select which sets of changes to commit/qrefresh"?

wow

>  share           (no help text available)
>
>     "share a common history between several working directories"?
>
>  transplant      patch transplanting tool
>
>     Just like the header to the longer description,
>     "transplant changesets from another branch"?
>
>  win32mbcs       allow to use MBCS path with problematic encoding.
>
>     Remove ending dot
>
>  win32text       (no help text available)
>
>     Again, need to upgrade (and improve) source comments as python
>     doc.
>
>     "preform automatic newline conversion"?
>
>  zeroconf        zeroconf support for Mercurial repositories
>
>     "discover and advertise repositories on the local network"?