[PATCH 1 of 1] churn: improve description
Martin Geisler
mg at lazybytes.net
Thu Jun 18 04:17:38 CDT 2009
timeless <timeless at gmail.com> writes:
> 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.
Me too :-)
>> "allow or deny access to parts of a repository"?
>
> parts => portions ?
> allow or deny => control ?
I like 'control' better; I'm okay with both 'parts' and 'portions'.
>> bookmarks Mercurial bookmarks
>>
>> "track a line of development with moving pointers"?
>
> I don't like 'pointers' but can't offer something better
Yeah, 'pointers' usually means something else when developing software.
I like Cédric's suggestion of 'markers', it fits better with the whole
'bookmark' concept.
>> 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?)
I think there's only being actively run, even though others could start
their own as Cédric noted somewhere else in the thread.
>> Simply "hilight syntax in hgweb"? Leaving information about
>> dependencies to the longer description.
>
> syntax highlighting for hgweb (and check the capitalization of 'hgweb')
Your suggestion is good and I think it's quite normal to write 'hgweb'
without capitalization since it refers to the Python module named
'mercurial.hgweb'. Or at least that's how I've always read it :-)
>> interhg (no help text available)
>
>> "use the InterWiki syntax in changelog and summaries"?
>
> use or support ? is this an input or output thing?
It's an output thing: it replaces things like 'Bug 123' with '<a
href="http://tracker/bug?id=123">bug 123</a>' in your commit message
when displayed in hgweb. I think this means that 'support' would be the
correct word?
>> parentrevspec use suffixes to refer to ancestor revisions
>
> use => support ?
>
>> patchbomb sending Mercurial changesets as a series of patch emails
>>
>> s/sending/send/ ?
Yeah, I like the more active form.
>> 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
I suggest
delete files not tracked by Mercurial from the working directory
>> 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"?
All good! I hope you can keep track of all the suggestions :-)
--
Martin Geisler
VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
More information about the Mercurial-devel
mailing list